Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Search Ruian

search_ruian
Read-onlyIdempotent

Search RUIAN addresses by fulltext through the IPEX API and optionally retrieve detail for matched records.

Instructions

Addresses found by fulltext (RUIAN). IPEX API: GET /v1/ruian/{fulltext}.

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": {
      "fulltext": "<fulltext>"
    },
    "name": "search_ruian"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoQuery parameter 'detail' of the IPEX API.
fulltextYesPath parameter 'fulltext' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds only the upstream endpoint path (GET /v1/ruian/{fulltext}), with no information on result completeness, pagination, empty-result behavior, or what 'detail' changes in the response.

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?

Two short, front-loaded fragments with no filler or repetition. It is efficient, though part of that efficiency comes from omitting information rather than from tight editing.

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

Completeness2/5

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

A search tool with two parameters, an open-world remote API call, and no output schema. The description gives the agent the endpoint but nothing about what a result record looks like, how matching is performed (prefix, substring, diacritics), or how to constrain a potentially large result set — gaps that matter for a search call.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3; the schema documents both parameters, though only as 'Path parameter' and 'Query parameter' of the IPEX API, which is near-tautological. The description's endpoint template reinforces that 'fulltext' is a path segment, but it adds no meaning for the 'detail' parameter, whose effect on output is never explained anywhere.

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

Purpose3/5

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

The description identifies the resource (addresses) and the lookup mode (fulltext against the RUIAN registry), which is more than the bare name provides. However, the phrasing is elliptical rather than a verb+resource statement, and it never contrasts with the sibling get_ruian_address, so an agent must infer that this is a fuzzy/free-text search versus a precise lookup.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternative. A sibling named get_ruian_address clearly exists in the same domain, yet the description makes no attempt to route the agent between the two.

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

Deploy Server

Other Tools