Skip to main content
Glama

Pumpkin

public_request_review

DestructiveIdempotent

Validate customer input and show the exact request for confirmation.

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>",
      "draft": "<draft>",
      "revision": "<revision>",
      "fields": "<fields>"
    },
    "name": "public_request_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftYes
fieldsYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and openWorldHint=true, yet the description frames the tool as a safe validate-and-display step, which undersells real side effects. It says nothing about whether previewing consumes state, whether a revision check can fail, or what permissions are needed. The only behavioral detail given ("for confirmation") is too thin for a destructive, open-world operation.

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?

Two clauses, no filler, and the validation/confirmation purpose is front-loaded. It is efficient but so short that the structure carries almost no actionable content.

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?

With four required parameters, a nested object, no output schema, and destructive annotations, the description needs considerably more: what the preview returns, what validation failures look like, and what happens on confirmation. None of that is present.

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 coverage is 25%: only "site" is documented, while draft, revision, and the nested fields object have no explanation anywhere. The description adds no meaning about what draft/revision represent (e.g., a draft handle and optimistic-concurrency version) or what the nested fields must contain.

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?

"Validate customer input and show the exact request" conveys a preview/confirmation step, but "request" is vague about the resource (a public form submission?), and nothing distinguishes it from siblings like prepare_form_submission or submit_form. The agent can guess the stage but not the object.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative is named. The sequencing relative to submit_form / service_request_prepare must be inferred from the tool name alone.

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