Skip to main content
Glama

query_standard

Search standards by number or title keyword, then optionally use an as-of date to determine whether each standard was effective or superseded at that time.

Instructions

按关键词查标准,并可带 as_of 做双时态判定:该日是否已生效、是否已被替代。

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": {
      "keyword": "<keyword>"
    },
    "name": "query_standard"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo判定基准日 YYYY-MM-DD(可选)
keywordYes标准号或题名关键词

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral trait that as_of triggers a bitemporal determination of effective/superseded status, which is real value. However, it says nothing about matching behavior (exact standard number vs. fuzzy title), result volume, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the core action front-loaded and the optional mode attached via '并可带 as_of'. No filler or repetition.

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 two-parameter read tool with no output schema, the description covers purpose and the non-obvious temporal semantics adequately. Only the shape of the returned matches and any matching-precision caveats are left unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3. The description earns above baseline by explaining what as_of actually produces – a determination of whether the standard was in effect and whether it has since been superseded – which is semantic meaning the schema's '判定基准日' alone does not convey.

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 states a specific verb and resource ('按关键词查标准' – query standards by keyword) and adds the optional bitemporal mode. An agent can tell what it does, though it does not explicitly differentiate itself from siblings such as check_timeline or check_udi.

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?

Usage is implied: supply as_of when you need point-in-time validity ('该日是否已生效、是否已被替代'). There is no explicit when-not guidance and no named alternative for related lookups, so the agent must infer the routing.

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