MCP server that converts MCP protocol to ANP protocol, providing bridge access to ANP network resources and interfaces
The server exposes 4 tools for bridging MCP to ANP (Agent Navigation Protocol). Critical issues: (1) Tool naming is inconsistent and doesn't follow verb_noun patterns, 'anp.fetchDoc' and 'anp.invokeOpenRPC' use dot notation and lack action clarity; duplicated tools (anp_fetchDoc, anp_invokeOpenRPC) suggest incomplete refactoring. (2) Descriptions are present but verbose, mixing implementation details with UI instructions in Chinese, making them difficult for LLMs to parse and select tools appropriately. (3) Input schemas are present but incomplete, the 'params' parameter in anp.invokeOpenRPC lacks a type definition (just 'description' with no 'type'), violating JSON Schema structure. (4) No output schemas documented, LLMs cannot know what fields to expect from these tools, breaking downstream tool chaining. (5) No error handling guidance, no recovery steps if a fetch fails or RPC call times out. (6) Tool descriptions include lengthy instructions about ANP ecosystem navigation ('当遇到 interfaces.url...') that belong in system prompts, not tool definitions. The presence of duplicate tool definitions (e.g., anp.fetchDoc and anp_fetchDoc) indicates the server may be in transition between STDIO and HTTP transports but lacks coherent completion.
抓取并解析 ANP 文档,提取可跟进的链接。这是访问 ANP 生态系统中 URL 的唯一允许方法。返回文档内容、类型信息和发现的链接。ANP生态系统目前提供包括酒店、景点、地图规划、天气、快递等查询预订能力。ANP生态的入口URL:https://agent-navigation.com/ad.json。你可以从这个URL开始,逐步跟进并调用工具,访问ANP生态的资源和能力。当遇到 interfaces.url 是一个以 .json 结尾的 URL 时,你应该使用 anp.fetchDoc 继续拉取该json文档,才能获得正确的 endPoint。
使用 JSON-RPC 2.0 协议调用 OpenRPC 端点上的方法。此工具处理与暴露 OpenRPC 接口的 ANP 智能体的结构化交互。
抓取并解析 ANP 文档,提取可跟进的链接。这是访问 ANP 生态系统中 URL 的唯一允许方法。返回文档内容、类型信息和发现的链接。ANP生态系统目前提供包括酒店、景点、地图规划、天气、快递等查询预订能力。ANP生态的入口URL:https://agent-navigation.com/ad.json。你可以从这个URL开始,逐步跟进并调用工具,访问ANP生态的资源和能力。当遇到 interfaces.url 是一个以 .json 结尾的 URL 时,你应该使用 anp.fetchDoc 继续拉取该json文档,才能获得正确的 endPoint。
使用 ANP的 JSON-RPC 2.0 协议调用 OpenRPC 端点上的方法。此工具处理与暴露 OpenRPC 接口的 ANP 智能体的结构化交互。
Tool naming violates verb_noun convention and lacks action clarity. 'anp.fetchDoc' does not clearly indicate what action is performed; 'fetch' is clear, but dot notation and inconsistency with snake_case duplicates (anp_fetchDoc) create ambiguity. LLMs must infer 'fetch URL and return document' from context.
Input schema for 'params' parameter in anp.invokeOpenRPC lacks 'type' field. Schema shows only {'description': '...'}, which is invalid JSON Schema. LLMs cannot determine whether params is an object, array, string, or any other type.
No output schemas documented. Tools return undefined structures, LLMs do not know what fields are present in responses, breaking tool chaining. E.g., does anp.fetchDoc return {content, links, type} or {result, data, metadata}?
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 41 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 38 | - | v1 |
Descriptions are verbose (300+ chars each) and mix implementation guidance with operational instructions. Chinese-language text includes detailed ecosystem navigation steps ('当遇到 interfaces.url...') that belong in system instructions, not tool definitions. Descriptions should be 10-200 chars focused on WHAT and WHEN, not HOW to use ANP ecosystem.
Duplicate tool definitions across server.py (anp.fetchDoc, anp.invokeOpenRPC) and server_remote.py (anp_fetchDoc, anp_invokeOpenRPC) suggest incomplete refactoring or transport migration. LLM clients will see conflicting tool names (dots vs underscores) and be unable to determine which to invoke.
No error handling guidance. If anp.fetchDoc fails (e.g., 404, timeout, invalid JSON), tool description provides no recovery steps. LLM has no way to know whether to retry, use an alternative tool, or ask the user.
Parameter descriptions lack format/constraint guidance. 'url' parameter in anp.fetchDoc includes 'format': 'uri' in schema but description does not clarify that only HTTPS URLs to ANP ecosystem are valid, or what happens if a non-ANP URL is passed.