Skip to main content
Glama

Cn Tax Policy Text

cn_tax_policy_text
Read-onlyIdempotent

Full original Chinese text of one State Taxation Administration policy document from cn_tax_policy_search, with its title, document number (文号), document date, the effective date stated in the text when one is given, and the publisher validity flag. Pass the id returned by the search.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
idYesDocument id from cn_tax_policy_search, e.g. "c102416/c5211343".

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
textNo
titleNo
sourceNo
document_dateNo
validity_flagNo
validity_noteNo
document_numberNo
effective_date_stated_in_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuine context beyond that: the payload is untranslated Chinese source text, not a summary, and the effective date is present only 'when one is given' in the text, signaling an optional/possibly-absent field. It does not state failure behavior for an invalid or stale id.

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 sentences, front-loaded with the resource and scope, then the operational instruction. The enumeration of returned fields is somewhat list-like and partly redundant with the output schema, but nothing is padding.

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?

Single required parameter, full schema coverage, annotations, and an output schema — the description covers what an agent needs to select and call it correctly. Remaining gaps (error handling for an unknown id, whether long documents are truncated) are minor given the structured fields available.

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 coverage is 100% and the sole id parameter already carries a description and example, so the schema does the heavy lifting. The description reinforces provenance ('returned by the search'), which is marginally useful but largely repeats what the schema already says.

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?

States a precise verb and resource: fetch the full original Chinese text of ONE State Taxation Administration policy document, sourced from cn_tax_policy_search. The word 'Full original' plus the explicit field list clearly separates it from the sibling search tool, which presumably returns abbreviated results.

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

Usage Guidelines4/5

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

'Pass the id returned by the search' establishes the required workflow — this tool is a second step after cn_tax_policy_search, not a standalone lookup. There is no explicit statement of when-not to use it or what happens with an id not from search, but the context is clear.

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.