Skip to main content
Glama
tresor4k

macalc

calculate_pet_age

Convert your pet's age to human-equivalent years for health monitoring. Input animal type, age, and breed size to get the equivalent human age.

Instructions

Convert pet age (dog/cat) to human-equivalent years. Use for pet health monitoring. Inputs: animal type, age years, breed size. Returns human-equivalent age. See list_bundles for related 'animaux' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
animalYes
age_yearsYes
sizeNo

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?

No annotations provided, so description must disclose behavioral traits. It describes a simple conversion with inputs and output, but no additional details on idempotency, side effects, or permissions beyond basic calculation.

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 efficient: one sentence covering purpose, inputs, and output, plus a brief cross-reference. Every sentence adds value, and it is front-loaded.

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 simple calculator tool, the description covers purpose, inputs, and output. It references related tools via list_bundles. An output schema exists, so return values are not required in description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only lists parameter names (animal type, age years, breed size) without explaining enum meanings or constraints, adding minimal value over the schema.

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?

The description clearly specifies the tool converts pet age (dog/cat) to human-equivalent years, with explicit mention of inputs and output. It distinguishes from siblings by referencing 'animaux' calculators in list_bundles.

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 description states 'Use for pet health monitoring' providing context, and references list_bundles for related calculators, but lacks explicit when-not-to-use or alternative sibling tools.

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