Skip to main content
Glama

intentions_set_birth_info

Idempotent

Call once to register the user's birth date/time/gender. Each call is a complete replacement — all 6 fields must be supplied. For fields the user does not know or prefers not to share, pass null explicitly (e.g. hour: null for unknown birth time, gender: null for unspecified). To update just one field, first call intentions_get_profile to fetch the current values, merge the user's new input, then call this tool with the full merged payload. Changes to the date, gender or a known hour (including setting a known hour back to null) are limited to 3 per calendar month (UTC); filling in a previously-null hour, or the minute, is always free. intentions_get_profile returns how many are left. Always pass birthPlace (the city of birth, e.g. "Portland, Maine") when the user gives it: readings then use the real moment of birth there, daylight saving included. Omit it only to keep the stored one; changing it is free. If the call fails with birth_time_needs_confirming, the clocks changed over that time at the birthplace: ask the user which it was and call again with birthTimeFold (0 = the earlier, 1 = the later). Returns the element profile.

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": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>",
      "hour": "<hour>",
      "minute": "<minute>",
      "gender": "<gender>"
    },
    "name": "intentions_set_birth_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesBirth day of month, 1–31.
hourYesnull if unknown
yearYesBirth year, 1920–2030.
monthYesBirth month, 1–12.
genderYesnull if unspecified
minuteYesnull if unknown; requires hour to also be non-null
birthPlaceNoCity of birth, optionally with region or country ("Portland, Maine"). Ask the user for it. Omit or null only to keep the stored birthplace.
birthTimeFoldNoOnly after a birth_time_needs_confirming error: 0 = the earlier of the two possible moments, 1 = the later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / birthPlace
      Added value: +{
      +  "description": "City of birth, optionally with region or country (\"Portland, Maine\"). Ask the user for it. Omit or null only to keep the stored birthplace.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / birthTimeFold
      Added value: +{
      +  "description": "Only after a birth_time_needs_confirming error: 0 = the earlier of the two possible moments, 1 = the later.",
      +  "enum": [
      +    0,
      +    1,
      +    null
      +  ],
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: complete-replacement semantics, explicit null requirements, monthly change limits, which changes are free, how to recover from the fold error, and what the call returns. This is exactly the kind of mutation/rate-limit detail annotations do not provide.

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?

Despite covering many operational details, the description is front-loaded and organized around the actual call flow: register, replace, handle nulls, merge updates, respect limits, handle birthplace, recover from fold error. Every sentence carries useful information.

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?

For a complex mutation tool with no output schema and only basic annotations, the description includes the essential return behavior, replacement semantics, rate limits, fallback workflow, and error handling. An agent has enough information to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents individual fields. The description adds workflow-level meaning for the required full payload, explicit null handling, birthPlace behavior, and birthTimeFold recovery context, though some of that overlaps with schema descriptions.

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 opens with a specific verb and resource: 'register the user's birth date/time/gender.' It clearly distinguishes this as the write/set operation versus the sibling read/update workflow involving intentions_get_profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to call it, how to handle partial updates via intentions_get_profile, when to pass birthPlace, and how to respond to birth_time_needs_confirming. The alternatives and conditions are named rather than left to inference.

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.