Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Age calculator: exact age from a date of birth and the next birthday

calc_age
Read-only

Exact age from a date of birth in years, months and days, total days lived, the weekday of birth, and the date of and days until the next birthday, measured today (UTC) or on any date you give. Use for age checks, forms and anniversaries. Example: birthdate=1990-05-17. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "birthdate": "<birthdate>"
    },
    "name": "calc_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoMeasure on this date, YYYY-MM-DD (default today)
birthdateYesDate of birth, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, non-idempotent behavior. The description adds genuinely non-structured context: cost of $0.01/call via x402 USDC or a card key, the first 25 free, failed calls free, and an explicit warning that repeats are not free because each call is charged. That billing/warning detail is exactly the kind of thing annotations cannot convey.

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?

The output enumeration and the measurement-date qualifier are front-loaded, followed by usage, example, and pricing. Sentences earn their place, though the closing pricing sentence is dense and could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully specifies what comes back, and it covers the input example, default behavior, cost model, and side-effect profile. Nothing an agent needs in order to call this correctly is missing.

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%, with both `birthdate` and `on` already documented including the YYYY-MM-DD format and default-today behavior. The description reinforces the default by specifying it is measured today in UTC, but adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 states a specific computation (exact age from a date of birth) and enumerates the full output set: years/months/days, total days lived, weekday of birth, and next birthday date and countdown. It never names sibling date tools like date_diff or date_info, so an agent must infer the boundary itself, but the output enumeration makes the tool's identity unambiguous.

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?

It gives concrete usage context ('age checks, forms and anniversaries') and a worked example (birthdate=1990-05-17). There is no explicit exclusion or routing advice against the many sibling date tools, which keeps it short of a 5.

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.