Skip to main content
Glama

Check a submission

submission_status
Read-onlyIdempotent

Read-only. Shows where a story submitted to Plot Speaks stands when its submission id and claim code match: received and waiting for a person, approved (with the story's link), or not accepted (with the reviewer's short note, if there is one). Changes nothing. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "id": "<id>",
      "claim_code": "<claim_code>"
    },
    "name": "submission_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe submission id from the receipt
claim_codeYesThe claim code from the receipt, e.g. ABCD-EFGH-JKMN

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 safety is covered; the description still adds the outcome model (three states, link on approval, optional reviewer note) and the interaction constraint to call it silently and never mention the tool. It does not say what happens when the id and claim code do not match, which is the main behavioral gap.

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?

Front-loaded with 'Read-only' and the outcome enumeration, which is efficient. However, the silent-call instruction is padded with several near-duplicate example phrases ('let me check', 'let me check on that', 'one moment', 'hang on'), and 'Read-only' plus 'Changes nothing' say the same thing twice.

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?

There is no output schema, so the description carries the return-value burden and does so well by naming each status and its payload. It stops short of covering the failure path (invalid or mismatched id/claim code) and whether the agent should surface the link to the user.

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 both parameters already carry descriptions explaining they come from the receipt, including the claim code format example. The only added meaning is the conjunction ('when its submission id and claim code match'), with no explanation of mismatch or error behavior, so the 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 and resource (shows where a submitted story stands) and enumerates the three possible outcomes: waiting for a person, approved with a link, or not accepted with a reviewer note. That level of specificity lets an agent distinguish it from submit_story or withdraw_submission without opening the schema.

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 only implied: the agent must have a submission id and claim code from a receipt, which suggests it is a post-submission check, but there is no explicit when-to-use, when-not, or named alternative. The long style instruction ('call it silently...') governs delivery, not tool selection.

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