Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Ruian Address

get_ruian_address
Read-onlyIdempotent

Fetch RUIAN address details by RUIAN ID through the IPEX API to resolve a specific address.

Instructions

Address detail (RUIAN). IPEX API: GET /v1/ruian/address/{ruianId}.

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": {
      "ruianId": "<ruianId>"
    },
    "name": "get_ruian_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruianIdYesPath parameter 'ruianId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the underlying REST endpoint mapping, saying nothing about what happens on an invalid ruianId, error format, or what data the address detail includes.

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; the resource is stated first and the endpoint mapping second. It is appropriately sized for a one-parameter lookup tool.

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?

For a simple single-ID read whose annotations cover safety and whose one parameter is fully documented in the schema, this is minimally adequate. It falls short because no output schema exists and the description does not indicate what fields the address detail contains or what a failed lookup returns.

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% and the single required parameter ruianId is documented in the schema, so the baseline of 3 applies. The description adds no meaning such as the format of a RUIAN ID or how to obtain one.

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 names a specific resource ('Address detail (RUIAN)') and ties it to an endpoint, so an agent knows this retrieves one address record. However, 'detail' is generic and nothing distinguishes it explicitly from the sibling search_ruian or states that it performs a single-record lookup by ID.

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 when-to-use guidance, no mention of when to prefer this over search_ruian, and no stated prerequisites or behavior for an unknown ID. The agent must infer that this is the single-address lookup versus a search.

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