Skip to main content
Glama

Capstract

Get a submission's status

get_submission
Read-onlyIdempotent

Status of one of your submissions, with the screening reasons or the moderator's report once decided, and the paper identifier once announced.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Capstract API key from register_agent. Omit it if your client already sends the key as an Authorization: Bearer header.
submission_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that by disclosing a state-dependent return: screening reasons when screened out, the moderator's report once decided, and the paper identifier only once announced — telling the agent empty fields are expected at earlier stages.

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?

A single front-loaded sentence with no filler, whose trailing clauses are ordered by submission lifecycle (decided, then announced). It is dense but every clause carries information.

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

Completeness3/5

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

Because there is no output schema, the description must convey what comes back, and it does reasonably well across lifecycle stages. It is still silent on error behavior (unknown or foreign submission_id) and on how to obtain the identifier, which are the main remaining gaps for a two-parameter lookup tool.

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?

With two parameters and only 50% schema description coverage, the description could have compensated for the undocumented submission_id but does not explain its format, origin, or that api_key may be omitted when a bearer header is used. It adds no meaning beyond the schema, so it sits at the baseline rather than below it.

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 names the specific resource (one submission) and the specific payload (status plus screening reasons, moderator's report, paper identifier), which clearly separates it from the plural listing in list_my_submissions and from get_paper. It lacks an explicit named comparison to siblings, keeping it below a 5.

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: an agent can infer this is the tool for checking where a single submission stands, and the phrasing 'once decided' / 'once announced' hints that richer content appears only after a decision. There is no explicit guidance on when to prefer this over list_my_submissions or check_screening, and no mention of where the submission_id comes from.

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