x-mcp

x_schema_discovery

Search the X API operation inventory to find matching endpoints when you know the intent but not the exact operationId or parameters.

Instructions

Search the generated X API operation inventory. Use this before calling a dedicated X endpoint tool when you know the intent but not the exact operationId or parameter set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x_schema_discovery"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`limit`	No
`query`	No
`method`	No
`authType`	No
`mutating`	No
`includeCatalog`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. The verb 'Search' implies a read-only operation, but the description does not disclose what the search returns, pagination, or any other behavioral details. This is a moderate gap for a discovery tool.

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

Conciseness5/5

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

Two sentences, each earning its place. The first states the core function, the second gives usage context. No filler.

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

Completeness3/5

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

The description covers the core purpose and usage timing, making it minimally viable for a discovery tool. However, the absence of any parameter descriptions and output information leaves the agent without guidance on how to craft searches or interpret results, given the lack of an output schema.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain any of the seven parameters (tags, limit, query, method, authType, mutating, includeCatalog). The parameter names are somewhat self-explanatory, but the description adds no specific semantics, so it fails to compensate for the lack of schema descriptions.

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

Purpose5/5

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

The description begins with 'Search the generated X API operation inventory', giving a specific verb and resource. It also distinguishes from the many sibling endpoint tools by positioning itself as a pre-call discovery step.

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

Usage Guidelines5/5

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

It explicitly states 'Use this before calling a dedicated X endpoint tool when you know the intent but not the exact operationId or parameter set', which provides clear when-to-use and implies the alternative (dedicated tools). This is strong guidance.

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

Deploy Server