Skip to main content
Glama

custody_calendar

Custody calendar: from the rule (alternating weeks or fixed weekdays, handover time, one-off swaps) who has the children each day, the handovers and an .ics file for any calendar (format=ics). Price: $0.01 USDC per call (x402).

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": {
      "from": "<from>"
    },
    "name": "custody_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
fromYes
langNoLanguage of the core texts (default it)
modeNo
startNo
formatNo
parent_aNo
parent_bNo
weekdaysNoFixed mode: {mon..sun: "a"|"b"}
overridesNo
first_parentNo
handover_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the two facts an agent most needs before calling: the tool is paid ($0.01 USDC per call via x402) and what it returns (daily assignment, handovers, .ics file). It omits timezone handling, date-format expectations for the required 'from' field, and failure behavior, which leaves real gaps for a scheduling computation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one dense sentence with the core purpose front-loaded, and every clause carries information. However the parenthetical list is run-on and mixes output description with input enumeration and pricing, making it harder to scan than a short structured description would be.

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

Completeness3/5

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

The tool is complex (12 parameters, nested objects, no output schema, no annotations), and the description sensibly compensates by describing the returned artifacts. It still leaves the meaning of the required date field, date formats, and timezone semantics unexplained, which is a meaningful gap for a date-driven computation with no schema documentation.

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 only 17% across 12 parameters, so the description must compensate and largely does not. It adds meaning for mode (alternate/fixed), handover_time, overrides ('one-off swaps'), and format=ics, but says nothing about the required 'from' versus 'start'/'days' distinction, parent_a/parent_b, first_parent, or the lang default — arguably the most error-prone inputs.

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 names the resource (custody calendar) and states precisely what it produces: who has the children each day, the handovers, and an .ics export. The parenthetical lists the rule inputs (alternating weeks, fixed weekdays, handover time, one-off swaps), so an agent can tell what computation is performed. It does not differentiate from siblings, though the sibling set contains nothing overlapping, so the practical ambiguity is low.

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?

Usage is implied through the rule types ('alternating weeks or fixed weekdays') and the format flag ('format=ics' for a calendar file), which hints at the two calling scenarios. There is no explicit when-to-use/when-not guidance, no statement about which rule mode requires which inputs, and no mention of alternatives for calendar export. Adequate but reliant on 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.

Resources