Skip to main content
Glama

Pumpkin

service_request_prepare

Prepare a request for a selected service and preferred time. Staff will review.

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": {
      "site": "<site>",
      "itemId": "<itemId>"
    },
    "name": "service_request_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
itemIdYes
detailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is already given. The description adds one genuinely new behavioral fact — that a human staff review follows — which matters for an agent deciding whether this finalizes anything. It does not say whether a persisted draft/ID is created, whether it can be edited or cancelled afterward, or what the call returns.

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, front-loaded with the core action and with no filler or repetition. It is efficient, though the terseness leaves the review semantics and return value unstated.

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

Completeness2/5

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

For a non-idempotent, non-read-only tool taking a free-form nested object with no output schema, the description is thin. An agent cannot learn what 'prepare' produces (a request ID, a pending record, a confirmation), what fields details accepts, or what follow-up call is expected, all of which matter before invoking it.

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 coverage is only 33%: 'site' is described in the schema, but 'itemId' and the nested 'details' object are not. The description partially compensates by mapping 'selected service' to the item parameter and 'preferred time' to information presumably carried in details. However, the shape and accepted keys of the nested details object remain undocumented in both places.

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?

States a concrete verb and resource: 'Prepare a request for a selected service and preferred time.' An agent can tell this is a draft-creation step rather than the submission itself. It stops short of naming the sibling service_request_submit that would complete the flow, so the prepare-vs-submit distinction has to be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus service_request_submit or the more general submit_form. 'Staff will review' hints at an asynchronous, reviewed workflow but does not tell the agent whether this must precede submission or can stand alone. Usage is only weakly 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