Skip to main content
Glama

Discover the Tools

get_submission_status

Read-onlyIdempotent

Retrieve only your submission status using its private receipt and tracking secret. Never reveal or request other inbox records.

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

Input Schema

NameRequiredDescriptionDefault
receiptYes
tracking_secretYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a privacy constraint about not exposing or requesting other inbox records, which is genuine context beyond annotations, but it says nothing about what status values or response shape to expect.

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 short sentences, front-loaded with the action and immediately followed by the confidentiality rule. Nothing is redundant or padded.

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?

For a simple two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, required credentials, and a privacy guardrail. The only gap is that it does not hint at what a 'status' result contains.

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 0%, so the schema carries only regex patterns for both credentials with no prose descriptions. The description identifies them as a 'private receipt' and 'tracking secret', conveying that they are caller-specific secrets, but it adds no format or sourcing guidance beyond that.

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 states a specific verb and resource ('Retrieve ... your submission status') and constrains scope to the caller's own submission. It is clear enough to distinguish from listing/search siblings, though it does not name an alternative explicitly.

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?

Usage is implied: you use this with a receipt and tracking secret after submitting a tool. There is no explicit when/when-not or reference to siblings like check_tool_listing, but the 'Never reveal or request other inbox records' line defines a hard boundary on what to ask for.

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