AiLinkAny

Inspect MCP tool declaration

get_tool_catalog_diagnostics

Read-onlyIdempotent

Read the exact registered MCP tools/list metadata for one named AiLinkAny tool through this already-authorized OAuth connection. Return annotations and description by default; set include_schemas=true when full input/output JSON Schema is needed. This is read-only, one tool per call, and never returns OAuth credentials, account secrets or private server settings. Use for troubleshooting tool compatibility, not for ordinary computer commands.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool_name": "<tool_name>"
    },
    "name": "get_tool_catalog_diagnostics"
  }
}

Input Schema

Name	Required	Description	Default
`tool_name`	Yes	Exact AiLinkAny tool name to inspect.
`include_schemas`	No	Also return the selected tool's actual input/output JSON Schemas and declared security schemes.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	Yes
`tool_name`	Yes
`catalog_tool_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: the call runs over an already-authorized OAuth connection, one tool per invocation, and the result deliberately excludes OAuth credentials, account secrets and private server settings. Error behavior for an unknown tool_name is not addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action and followed by defaults, conditional behavior, then scope limits. Every sentence carries information, though the trailing "not for ordinary computer commands" clause is the weakest and slightly repetitive of the troubleshooting framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. It nonetheless covers what is returned by default versus on request, what is intentionally withheld, and how many tools can be inspected per call, which is everything an agent needs to invoke this two-parameter diagnostic correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description goes slightly further by explaining the purpose of include_schemas (fetching full input/output JSON Schema, not just annotations and description) and by warning that only one exact tool name per call is accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: read the registered MCP tools/list metadata for one named AiLinkAny tool, and scopes it to a single tool per call. It does not, however, distinguish itself from the very similar-sounding sibling mcp_gateway_describe_tool or mcp_gateway_list_tools, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("Use for troubleshooting tool compatibility") and an exclusion ("not for ordinary computer commands"), plus a conditional rule for the optional parameter (set include_schemas=true when full JSON Schema is needed). The exclusion is slightly weak because it does not name the tool the agent should use for ordinary commands instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AiLinkAny tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?