Skip to main content
Glama

Pumpkin

submit_form

DestructiveIdempotent

Send the visitor-reviewed form after permission and verification.

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": "submit_form"
  }
}

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.4/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true, idempotentHint=true, and openWorldHint=true, and the description does little to explain those traits beyond a passing reference to 'permission and verification'. It never says what is destroyed or consumed (e.g., whether the 'proof' token is single-use given idempotentHint=true), nor what an irreversible submission means to the visitor.

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?

It is a single efficient sentence with no filler, so there is no wasted wording. The problem is under-specification rather than verbosity — brevity here costs more than it saves.

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, 25% schema coverage, no output schema, and a destructive annotation, this definition leaves too much unexplained for a high-stakes submission tool. It does not cover prerequisites, token sourcing, consent semantics, or what success/failure looks like.

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 25%: only 'site' is documented, while 'proof', 'consent', and 'captchaToken' carry no description in either the schema or the description. The description should have explained where 'proof' comes from and what 'consent' affirms, but provides nothing to compensate for the coverage gap.

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 verb 'Send' and resource 'form' are present, but the phrase 'visitor-reviewed form after permission and verification' is loose enough that an agent cannot confidently distinguish this from siblings like prepare_form_submission or service_request_submit. It states a general action without pinning down what exactly is transmitted or to whom.

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?

The only usage cue is the vague 'after permission and verification', with no explicit statement that prepare_form_submission must run first, no when-not-to-use guidance, and no mention of how it differs from the other submit_* siblings. An agent must infer the preconditions and ordering from the 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