Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

宠物养护周期速查表

pet-care-schedule

宠物养护周期速查表:猫狗洗澡、剪指甲、刷牙、清耳、梳毛、驱虫到底多久做一次?按猫/狗、幼年/成年/老年、短毛/长毛生成一份可抄做的养护周期表,每项附避坑提示。日常养护经验参考,异常请就医。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "animal": "<animal>",
      "ageStage": "<ageStage>",
      "coat": "<coat>"
    },
    "name": "pet-care-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
coatYesshort(短毛)/ long(长毛)
animalYescat(猫)或 dog(狗)
ageStageYesyoung(幼年)/adult(成年)/senior(老年)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description must carry the full behavioral load; it does disclose the output shape (a copyable cycle table with a pitfall tip per item) and that results are deterministic. However, it never states that the tool is pure computation with no side effects or data storage, and the '确定性计算结果与依据' phrasing is boilerplate rather than a concrete guarantee about the response.

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 purpose and coverage are front-loaded in the opening sentence, but the rhetorical question ('到底多久做一次?') and the trailing template sentences about deterministic results and model arithmetic instability consume space without informing the caller. Roughly a third of the text does not earn its place.

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 three-parameter, read-only-style lookup tool with no output schema and no annotations, the description covers the domain, the segmentation dimensions, the output form and a safety disclaimer. The remaining gap is the boilerplate usage sentence, which is irrelevant rather than missing information.

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 description coverage is 100% and all three parameters are documented in the schema with their value sets, so the baseline is 3. The description restates the same three dimensions (cat/dog, young/adult/senior, short/long coat) and confirms they combine to shape the schedule, but adds no format, default, or edge-case meaning beyond the 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 a concrete resource and output: a pet-care cycle table covering bathing, nail trimming, teeth brushing, ear cleaning, grooming and deworming, segmented by cat/dog, young/adult/senior and short/long coat. It also implicitly separates itself from medical advice ('异常请就医'), which helps against the pet-first-aid sibling, though no sibling is named explicitly.

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?

The only usage line is templated boilerplate ('模型算数不稳、法规口径易错时,调用它拿准确答案') that has little to do with pet-care scheduling and reads as copy-paste from a calculation-tool template. There is no guidance on when to pick this versus pet-age or pet-first-aid, and no prerequisites or exclusions beyond the generic vet disclaimer.

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