Skip to main content
Glama

freehire

Add a dated mock schedule override

buddy_mock_schedule_add_override

Add one dated override to the person's hosting schedule: on that date they host between start and end (HH:MM) instead of their weekly hours. An equal start and end closes the date. Returns the stored rule with its id.

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": {
      "date": "<date>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "buddy_mock_schedule_add_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd of the window, HH:MM; 24:00 means until midnight.
dateYesThe date, YYYY-MM-DD.
startYesStart of the window, HH:MM in the person's mock time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds real behavioral content: it discloses the mutation effect ('on that date they host between start and end instead of their weekly hours'), the edge-case effect ('An equal start and end closes the date'), and the return shape ('Returns the stored rule with its id'). It does not state whether an existing override on the same date is replaced or rejected, which matters given idempotentHint=false.

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?

Two sentences, zero filler. The core action and scope are front-loaded, the edge case follows, and the return value is stated last. Every clause carries information an agent would otherwise have to guess.

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 3-parameter mutation with no output schema, the definition is nearly complete: it explains the window semantics, the closing case, and what comes back. The remaining gap is collision behavior on a date that already has an override, which is the one thing an agent could get wrong given idempotentHint=false.

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 a 3 would be the baseline. The description goes beyond it by framing start/end as a hosting window and by stating the non-obvious semantic that equal start and end closes the date — meaning not conveyed by the schema, which only documents the 24:00 midnight convention.

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 opens with a specific verb+resource pair ('Add one dated override to the person's hosting schedule') and scopes it to a single date with a start/end window. It implicitly contrasts with the recurring schedule via 'instead of their weekly hours', though it never names buddy_mock_schedule_set_weekly directly.

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 by the phrase 'instead of their weekly hours', which signals this is the one-off path rather than the recurring one, and the equal-start/end case is explained. However, no sibling is named and there is no explicit when-not-to-use guidance (e.g. use set_weekly for recurring hours, use schedule_delete to remove).

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.