Skip to main content
Glama

Look up the registered taxpayer's personal data

rfc_profile
Read-only

Look up the registered taxpayer's personal data. Asks the government registry for real and is billed to the connected account: see get_account for what it costs you. Only send identifiers the user gave you. Details: read_doc "rfc/endpoints/profile".

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": {
      "rfc": "<rfc>"
    },
    "name": "rfc_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfcYesThe RFC number to validate (12 or 13 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds value beyond them: it discloses that a real government registry is queried and the call is billed to the connected account, pointing at get_account for cost. That billing disclosure is genuinely new information an agent needs before invoking a paid endpoint.

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?

Purpose is front-loaded in the first sentence and every following sentence adds a distinct fact: billing, privacy constraint, and a documentation pointer. The trailing 'Details: read_doc "rfc/endpoints/profile"' is slightly awkward phrasing but not wasteful.

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

Completeness4/5

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

For a one-parameter lookup with annotations covering safety and no output schema, the description covers purpose, external dependency, cost, and privacy adequately. It could say a little more about what personal data fields come back, since there is no output schema to fall back on.

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?

The single parameter has full schema description coverage (12 or 13 characters), so the schema carries the semantics and baseline 3 applies. The description contributes only the data-hygiene rule that identifiers must come from the user, not additional format or validation meaning.

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: 'Look up the registered taxpayer's personal data', which is clearly distinct from validation tools like rfc_validate or rfc_verify. It does not explicitly name the sibling it contrasts with, so the agent must infer that this retrieves data rather than merely validating the RFC format.

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

Usage Guidelines3/5

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

Offers a real constraint ('Only send identifiers the user gave you') and routes the agent to get_account for pricing and read_doc for endpoint details. However, it never says when to pick this over rfc_validate, rfc_verify, or csf_verify, leaving the key selection decision to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources