Skip to main content
Glama
Sign In

DogsLife

by com.dogslifeapp
OverviewDiscussionsAdmin

Dog walk and exercise needs

calculate_dog_walk_needs
Read-onlyIdempotent

Works out how much walking and exercise a dog needs per day for its age, size and energy level. Puppies (until about 12 months, large breeds 18 months): the 5-minutes-per-month-of-age rule for formal walks, up to twice a day, never above the adult amount for the dog's type. Adults: the Royal Kennel Club daily bands (up to 30 minutes, up to 1 hour, or more than 2 hours). For questions about how long to walk a puppy or a dog, or how much exercise a breed type needs. General guidance from kennel-club and vet sources (Royal Kennel Club, PDSA, AniCura), not veterinary advice.

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": {
      "age": "<age>"
    },
    "name": "calculate_dog_walk_needs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesThe dog's age, in the unit below (8 weeks to 20 years).
sizeNosmall = small or medium breed (grown at about 12 months); large = large or giant breed (grown at about 18 months).small
unitNoUnit of age.months
energyNoBreed energy: low (up to 30 min a day as an adult), moderate (up to 1 hour), high (more than 2 hours, e.g. working and herding breeds).moderate
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 and openWorld=false, so the bar is lower. The description adds real value beyond them: the underlying rules applied (5-minutes-per-month, Kennel Club bands), source attribution, and an explicit 'not veterinary advice' caveat.

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?

Four sentences, front-loaded with the core purpose, then the rules, then usage triggers, then the disclaimer. Slightly dense with parenthetical detail but nothing is clearly 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?

For a read-only calculator with full schema coverage and no output schema, an agent has enough to call it correctly. It does not describe the shape of the returned answer (e.g., minutes per walk vs. per day), which is the only notable gap.

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 all five parameters including enums and defaults are already documented. The description restates the puppy age thresholds and adult bands, which largely duplicate the size and energy enum descriptions rather than adding new parameter-level meaning.

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?

Opens with a specific verb+resource: 'Works out how much walking and exercise a dog needs per day', scoped by age, size and energy. It is clearly a domain calculator and distinct from siblings like calculate_dog_human_age, calculate_puppy_feeding_schedule or calculate_puppy_sleep_needs.

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?

Explicitly states the triggering questions: 'For questions about how long to walk a puppy or a dog, or how much exercise a breed type needs.' No sibling tool is named as an alternative, so it stops short of a 5, but the usage context is unambiguous.

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

All DogsLife toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources