AGILEX Docs
v1.9.2Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.
Endpoint health
online- Last checked
- 11/20/2026, 9:17:27 AM
- Latency
- 732 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.agilex.service%2Fdocs
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.agilex.service/docs": {
"url": "https://service.agilex.ai/agilex-docs/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
find_in_doc
Locate a passage *inside* one manual, without paging through it. Use this after ``search_docs`` whenever you need a specific table, command or error code rather than the whole page — including short documents, because manuals commonly open with a preamble and page 1 rarely answers a question. It returns the exact ``offset`` of each match, so one ``get_doc(doc_id, offset=...)`` lands on the right section. Prefer this over repeatedly calling ``get_doc`` with increasing offsets. Args: doc_id: id from ``search_docs`` (also accepts the page slug). query: the *concept*, not the product name — e.g. "波特率" or "急停 接线". Terms that already appear in this page's title are ignored, because ``search_docs`` picked the page by them; passing the product name again only adds noise. Generic words that appear in nearly every manual are down-weighted, so one distinctive term is enough. limit: 1-10 passages, default 5. Matching is OR, not AND: a passage is returned when it contains at least one term with enough weight. Terms that are absent from this page therefore do **not** force a zero result — check ``missing_terms`` to see which of your words this page never mentions, and ``matched_terms`` for the ones it does. A query made only of stop words (or nothing) returns ``count: 0`` with a hint. Returns JSON: {doc_id,title,space,url,chars,query,count,returned, matched_terms,missing_terms,hits:[{offset,heading,score,matched,excerpt}], hint}. ``count`` is the total number of matched passages; ``returned`` is how many are in ``hits`` (capped by ``limit``). ``heading`` is the nearest heading above the passage; ``offset`` is absolute in the page body.
Schema valid · SHA-256 d3bb321623ff…
View input schema
{ "type": "object", "properties": { "doc_id": { "title": "Doc Id", "type": "string" }, "query": { "title": "Query", "type": "string" }, "limit": { "default": 5, "maximum": 10, "minimum": 1, "title": "Limit", "type": "integer" } }, "required": [ "doc_id", "query" ], "title": "find_in_docArguments" }
Connections
streamable-http
https://service.agilex.ai/agilex-docs/mcp