Skip to main content
Glama

Pumpkin

prepare_form_submission

Prepare a selected form for the visitor to review. Collect contact information in the form.

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>",
      "type": "<type>"
    },
    "name": "prepare_form_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
typeYes
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description usefully adds that this stages a form for visitor review rather than submitting it, which explains the non-read-only, non-idempotent nature. It stops short of saying what state is created, whether a handle/token is returned, or what happens on repeated calls.

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 with no filler, and the purpose comes first. Brevity here is efficient rather than padded, though the second sentence is so vague it earns little.

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-read-only tool taking a free-form nested 'fields' object with no output schema, the definition leaves too much open: no description of what 'type' accepts, no structure for 'fields', and no indication of what the caller receives or does next. The complexity here demands more than two sentences.

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 33%: 'type' and the nested 'fields' object are undocumented in the schema. The description's 'collect contact information in the form' is only a faint hint, giving no field names, nesting rules, or shape for the 'fields' object that is the tool's core payload.

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/resource pair ('Prepare a selected form') is stated, and the second sentence hints at collecting contact data, but 'prepare' is ambiguous about what is actually produced. It never distinguishes itself from siblings like get_public_form (fetching a form) or submit_form (finalizing it), so an agent must guess where this sits in the flow.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. The mention of 'for the visitor to review' implies a pre-submission step but never says to prefer this over submit_form or get_public_form, which is exactly the distinction an agent needs.

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