Skip to main content
Glama

Tallyho

Read a booking

status
Read-only

Read a booking as it stands, by booking_id, from any session; holding the booking_id is enough. Works on every booking, handoff ones too. On a booking Tallyho is calling about, status moves from requested to confirmed, counter, declined, not_booked or pending: call status again after check_after_s seconds, and stop when check_after_s is absent. Never tell the user a job is booked unless booked is true. Returns the quote once known, the reason a booking fell through or was countered, the promises still to report, and, if it fell through, the next best plumbers from the same search. Reads only; never contacts a business.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes

Output Schema

NameRequiredDescriptionDefault
jobYes
callNo
quoteYes
bookedYes
reasonYes
statusYes
channelYes
handoffYes
billableYes
businessYes
booking_idYes
environmentYes
alternativesYes
contact_usedYes
report_afterYes
check_after_sNo
contract_versionYes
still_unobservedYes
promises_in_scopeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint false; the description adds the state machine (requested to confirmed/counter/declined/not_booked/pending), the terminal condition, the cross-session access property, and the hard rule never to report a job as booked unless booked is true. That is substantive behavior beyond what the annotations carry, and nothing contradicts readOnlyHint.

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?

Front-loaded with the action and access rule, then polling semantics, then return contents. Dense but mostly earns its space; the sentence enumerating returned fields (quote, failure reason, promises, next best plumbers) partly duplicates the provided output schema.

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 one-parameter read tool with an output schema and read-only annotations, the description covers everything an agent needs: how to call it, whether auth/session matters, how to poll, when to stop, and the guardrail on reporting success. Return-value explanation is a bonus rather than a gap filler, since an output schema exists.

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?

The single parameter has 0% schema description coverage, so the description must carry the meaning, and it does explain that booking_id alone is sufficient and that no session scoping is required. It adds no format or length guidance beyond that, leaving the schema's maxLength/minLength constraints to speak for themselves.

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?

"Read a booking as it stands, by booking_id" gives a specific verb and resource, and "Reads only; never contacts a business" separates it from the book/contact flow. It never explicitly contrasts itself with the sibling tools (report, find), so sibling differentiation is implied rather than stated.

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?

Gives explicit entry conditions (any session, holding the booking_id is enough, works on handoff bookings too) and explicit polling guidance: on an in-flight booking call status again after check_after_s seconds and stop when check_after_s is absent. That is a full when-to-call and when-to-stop contract.

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