Skip to main content
Glama

Pumpkin

service_request_submit

DestructiveIdempotent

Send a reviewed service request to staff.

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>",
      "proof": "<proof>",
      "captchaToken": "<captchaToken>",
      "consent": "<consent>"
    },
    "name": "service_request_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
proofYes
consentYes
captchaTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, openWorldHint=true and idempotentHint=true, and the description is consistent with a write action ('Send'), so no contradiction. However, it adds almost nothing beyond them: it does not say the request leaves the system to external staff, that submission cannot be undone or recalled, or that a captcha and consent are prerequisites for a successful call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is well structured. At this length for a four-required-parameter destructive mutation, the brevity reflects under-specification rather than efficiency.

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 destructive, open-world submission with four mandatory parameters and no output schema, an agent needs to know where the proof and captcha token originate and what the staff delivery implies. Neither is covered, so the definition is not sufficient to call the tool correctly without external inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, and only the 'site' parameter is documented (as an ID from find_business). The description explains nothing about 'proof', 'consent', or 'captchaToken' – where the proof value comes from, what consent represents, or how the captcha token is obtained – leaving three required parameters 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?

The description gives a concrete verb ('Send') and resource ('service request') plus a scoping qualifier ('reviewed'), which separates it from sibling service_request_prepare. It stops short of naming the alternative it supersedes, 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 word 'reviewed' implies this is the terminal step after preparing/reviewing a request, which is useful implied sequencing. It never states prerequisites explicitly, nor when the agent should call service_request_prepare or public_request_review instead, so guidance remains inferential.

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