Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

猫龄狗龄换算器

pet-age

猫龄狗龄换算器:把猫咪/狗狗的实际年龄换算成人类年龄,判断它处在幼年、成年还是老年。猫按通行分段对照,狗区分小型/中型/大型犬(体型越大衰老越快),并提示常见误区。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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>",
      "years": "<years>",
      "size": "<size>"
    },
    "name": "pet-age"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes仅狗需要:small/medium/large(小型/中型/大型犬)
yearsYes实际年龄(岁,可含小数,如 2.5)
animalYescat(猫)或 dog(狗)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the computation is deterministic, that the response includes both the result and its basis (依据), that cats use standard bands while dogs are split by breed size, and that common misconceptions are flagged. It stops short of explicitly stating there are no side effects or state changes, so it is not quite exhaustive.

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?

Front-loads purpose, then method, then usage scenario, in a compact flow with no wasted sentences. The line about passing a parameter object and getting a deterministic result is somewhat boilerplate but does add a small amount of expectation-setting.

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 stateless three-parameter calculator with no output schema, the definition covers what it computes, how the bands differ by species/size, and that the answer comes with justification. Nothing critical is missing, though a note on output shape (e.g., human age plus category label) would close the last gap.

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 is 3, but the description adds real meaning beyond the schema: it explains why 'size' exists (larger dogs age faster) and that only dogs need it, giving the agent a rationale for populating the field rather than just an enum list. It does not clarify valid ranges for years beyond the schema's own example.

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 concrete verb+resource pair: converting a real cat/dog age into a human-equivalent age and classifying it as young/adult/senior. This is clearly distinct from the pet-care-schedule and pet-first-aid siblings, which handle scheduling and emergency response rather than age arithmetic.

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?

Gives an explicit trigger context — use it when model arithmetic is unreliable or when regulatory/standard conventions are easy to get wrong — which tells the agent when this tool beats doing the math inline. It does not name an alternative tool or a when-not condition, but the usage 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.

Resources