Skip to main content
Glama
tresor4k

macalc

calculate_dog_age

Convert dog age to human years using the AAHA veterinary method. Input dog age in years and breed size (small, medium, large, giant) to get the equivalent human age for health monitoring.

Instructions

Convert dog age to human-equivalent years using modern AAHA method. Use for canine health monitoring. Inputs: dog age years, breed size. Returns human-equivalent age. See list_bundles for related 'animaux' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dog_yearsYesDog age in years
sizeNoDog sizemedium

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

With no annotations, the description must convey behavioral traits. It mentions the AAHA method and returns human-equivalent age, but does not disclose side effects, permissions, or output format details. The presence of an output schema compensates somewhat, but the description itself is minimal.

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?

The description is concise with two sentences and a reference to list_bundles. Every sentence adds value with no wasted words, making it efficient and easy to parse.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the core purpose, method, and inputs adequately. It could mention return value format or edge cases, but overall it is sufficiently complete.

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 description adds little beyond the schema. It lists 'dog age years, breed size' but does not elaborate on the breed size values or provide examples. Baseline 3 is appropriate.

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 clearly states the tool converts dog age to human-equivalent years using the AAHA method, specifying the verb and resource. However, it does not explicitly differentiate from other pet age calculators, like calculate_cat_age or calculate_pet_age, missing a chance to distinguish.

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?

The description suggests use for canine health monitoring and references list_bundles for related calculators, but it does not specify when not to use this tool or indicate alternatives. Guidance is implied but lacks explicit exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server