Skip to main content
Glama

Dog age in human years

calculate_dog_human_age
Read-onlyIdempotent

Converts a dog's age (1 to 16 years) into human years using the American Veterinary Medical Association chart (about 15 human years at 1, 24 at 2, then about 4 to 6 per year), and says when dogs are usually considered seniors. For questions like how old a dog is in human years.

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": {
      "years": "<years>"
    },
    "name": "calculate_dog_human_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYesThe dog's age in whole years, 0 to 16.
monthsNoExtra months on top of the years, 0 to 11.
languageNoThe language the user is writing in, as a language code (e.g. en, de, sv, pt-BR, es-MX, ja, ar). The answer comes back in that language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, closed-world, so the safety profile is covered. The description adds real value beyond that: the exact conversion basis, that the result is qualitative (senior status), and that the answer is localised to the user's language.

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 sentences, front-loaded with the conversion method and ending with the use case. Slightly dense with parenthetical numbers but nothing is wasted.

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?

There is no output schema, but the description tells the agent what comes back (a human-years figure plus a senior-status statement) in the user's language. Only mild gap is the unexplained months parameter.

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%, so the baseline is 3; the description only echoes the years range (and even that conflicts slightly, saying 1 to 16 where the schema allows 0 to 16). The months parameter and the language parameter are never mentioned in the description.

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 specific verb and resource (converts dog age to human years) and pins down the method (AVMA chart with the 15/24/4-6 progression) plus the senior-life-stage note. Clearly distinguishable from the sibling puppy/weight/walk calculators.

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?

The closing sentence 'For questions like how old a dog is in human years' gives the triggering question type, which is enough for an agent to route to it. No explicit exclusions or named alternatives, but the sibling names are obviously different calculations.

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.