Skip to main content
Glama

AutoTasker Hub — China Social Data API

cn_id_validate

Chinese resident ID checksum + province + birth + sex. Local compute. $0.01 USDC.

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": {
      "id": "<id>"
    },
    "name": "cn_id_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does contribute real behavioral context: 'Local compute' signals no external network dependency and '$0.01 USDC' discloses a per-call cost, neither of which is available in structured fields. However, it never says what happens when the checksum fails (error, throw, or a boolean field), whether calls are cached/billed on failure, and gives no auth or rate-limit information for 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?

Extremely compact and front-loaded: what it computes first, then compute locality, then price. No filler sentences. The trade-off is that the fragment style ('checksum + province + birth + sex') sacrifices readability and leaves out information an agent would want for the same token budget.

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 cheap, single-parameter, local utility this covers the essentials — what it computes, that it is local, and cost. But with no output schema, the description should say more about return shape (field names, what an invalid ID yields, whether province comes back as a code or name), and it says nothing about failure semantics or pricing edge cases.

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% for the single required 'id' parameter, so the description must compensate. It only implies the input is a Chinese resident ID number via the topic; it adds no format constraints (length, digit structure, checksum character position, whether spaces or lowercase x are accepted). That is the bare minimum compensation for a 0%-coverage schema.

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?

The description names the specific resource (Chinese resident ID) and enumerates the concrete computations it performs: checksum verification plus province, birth, and sex extraction. An agent can tell this is a deterministic ID-number parser/validator. It stops short of a full verb-and-object sentence (it reads as telegraphic fragments and leans on the tool name for the 'validate' verb).

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 mention of when not to use it. The narrow 'Chinese resident ID' scope is implied, but an agent must infer on its own that this applies only to mainland 18-digit resident IDs and not passports, HK/Macau IDs, or other national identifiers.

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.