Skip to main content
Glama

Pick a time to visit

commit_pick_time
Destructive

The card's time picker calls this tool. The assistant does not call it.

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": {
      "negotiationId": "<negotiationId>",
      "commitmentId": "<commitmentId>"
    },
    "name": "commit_pick_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotNoThe time the buyer picked, or null.
pickTokenNoThe token the card holds.
commitmentIdYesThe id of the choice.
negotiationIdYesThe id of the offer.
idempotencyKeyNoThe key the card holds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a mutating, externally visible operation. The description adds only the invocation-source fact and says nothing about what changes, whether a prior pick is replaced, how idempotencyKey/pickToken affect retries, or what happens on conflict — the most important behavioral detail for a destructive commit.

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 short sentences, front-loaded with the one fact that matters most for an agent (do not call this). No filler, no restating of the title.

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?

Because the description explicitly bars the assistant from invoking it, the completeness burden is lower than for a normal destructive 5-parameter tool. Still, if an agent ever does route here or must explain the flow to a user, nothing about the resulting state change is described and there is no output schema to fall back on.

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%, so each of the five fields is already documented in the schema. The description adds no meaning about slot=null semantics, how pickToken and idempotencyKey relate, or the difference between negotiationId and commitmentId, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the triggering context ('the card's time picker') and implies that a picked slot is being committed, but it never states the actual effect of the call — locking in a visit time, mutating the negotiation/commitment state, etc. The name plus trigger context makes the intent inferable, but the verb+resource statement is absent.

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 an unusually explicit exclusion: 'The assistant does not call it.' That is a clear when-not rule that no sibling name could supply. It stops short of telling the agent what to use instead for time-related tasks (visit_times, commit_confirm, book_visit), so it is not 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.

Resources