Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

宠物居家应急速查

pet-first-aid

宠物居家应急速查:猫狗突发剪甲出血、误食异物、中暑、呕吐、外伤,到场前该怎么一步步处理、什么情况必须立刻送医?按场景给物理处置步骤、千万别做的事和就医红线。只做处置与判断,不含任何用药或诊断。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "scene": "<scene>"
    },
    "name": "pet-first-aid"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYesnail-bleed(剪甲出血)/ swallow(误食)/ heatstroke(中暑)/ vomit(呕吐)/ wound(外伤)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior: output is a deterministic lookup result with its rationale, limited to physical handling and judgment, explicitly excluding medication and diagnosis — a meaningful safety boundary. It stops short of stating that the tool is read-only/side-effect free or what the response looks like structurally.

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

Conciseness3/5

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

The first half is well front-loaded and dense with relevant detail. The trailing two sentences ('传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时…') are generic template boilerplate that does not apply to a pet first-aid lookup and should have been cut.

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, read-only reference tool with no output schema, the description covers what it returns (steps, prohibitions, escalation red lines) and what it refuses to cover (drugs, diagnosis). The only gap is the misleading boilerplate, which could cause a wrong expectation about the tool's domain.

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 single 'scene' parameter already enumerates its five accepted values with glosses. The description restates those same scenes in prose (剪甲出血、误食异物、中暑、呕吐、外伤) without adding syntax, defaults, or edge-case handling, so it neither helps nor hurts beyond the schema baseline.

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 a specific resource and scope: step-by-step pre-vet physical handling for five named pet emergency scenes (nail bleed, ingestion, heatstroke, vomiting, wound), plus never-do items and vet red lines. The appended boilerplate about 'unstable model arithmetic' and 'error-prone regulatory standards' is irrelevant to pet first aid and slightly muddies the purpose, but the core verb+resource is unmistakable.

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?

It gives a clear trigger (a pet emergency at home, what to do before reaching the vet) and an explicit scope exclusion — no medication, no diagnosis — which routes the agent away for those needs. It does not differentiate from related siblings such as pet-care-schedule or pet-age, but the guidance for this tool's own use is unambiguous.

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