Skip to main content
Glama

get_submission_status

Read-onlyIdempotent

Receipt status for a submission made to POST /api/lead, by its submission_id (UUID v4). Reports receipt metadata only (received, when, intent, sandbox or real) — never the inquiry contents.

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": {
      "submission_id": "<submission_id>"
    },
    "name": "get_submission_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYesThe UUID v4 used when submitting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real value on scope: it enumerates the receipt fields returned (received, when, intent, sandbox or real) and explicitly excludes inquiry contents, which tells the agent what it can and cannot learn. It does not disclose behavior for an unknown or expired submission_id.

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

Conciseness5/5

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

Two sentences, front-loaded with the purpose and identifier, followed by the result boundary. No filler or redundant restatement of the name.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating the receipt metadata fields and ruling out inquiry contents, which is exactly what an agent needs to decide whether the call answers its question. The remaining gap is failure behavior for an invalid or unknown submission_id.

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 100% and the single parameter is documented as 'The UUID v4 used when submitting.' The description repeats the UUID v4 constraint without adding format, validation, or error semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (receipt status for a submission) tied to a concrete endpoint (POST /api/lead) and keyed by submission_id. It goes further to define the boundary of the result: 'receipt metadata only ... never the inquiry contents,' which no sibling tool overlaps with.

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

Usage Guidelines4/5

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

The context of use is clear — this is a post-submission receipt lookup keyed on the UUID returned when submitting to POST /api/lead. It implicitly excludes content retrieval, but it never names an alternative tool or states what to do if the ID is unknown, so routing guidance stops short of explicit when/when-not.

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