Skip to main content
Glama

Accept the time the mover suggested.

accept_appointment_time

Accept the time the mover suggested. Both sides get a calendar file. Scope: jobs:write.

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": {
      "job_id": "<job_id>"
    },
    "name": "accept_appointment_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id (ULID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-open-world operation, so the description does not need to restate safety. It adds genuine context beyond those annotations by disclosing the side effect ('Both sides get a calendar file') and the required auth scope ('jobs:write'), which are exactly the facts an agent needs before committing.

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?

Two short sentences plus a scope tag, with the action stated first and the side effect second. Nothing is wasted, though 'Scope: jobs:write' is telegraphic and would read better as explicit prose about required permissions.

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 single-parameter mutation with annotations and no output schema, the description covers purpose, side effect, and auth scope, which is most of what an agent needs. It omits error/precondition behavior (e.g., failure when the mover has not proposed a time) and any mention of what the calendar file delivery implies for the caller.

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 description coverage is 100% and there is a single required job_id already documented as a ULID in the schema. The description adds no format, constraint, or identification guidance beyond that, 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 names a specific verb and resource ('Accept the time the mover suggested') and ties it to a single job id, which clearly separates it from request_appointment or list_appointment_times. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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?

The phrase 'the time the mover suggested' implies the precondition that a suggestion already exists, but it never states when to use this instead of request_appointment or cancel_appointment, and it does not say what to do if no suggestion is pending. Usage is only implied.

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