Skip to main content
Glama

Submission status

submission_status
Read-onlyIdempotent

What became of an agent you submitted with register_agent: queued, crawled or not, what was found (listings, tools), why nothing was listed if so, and when it will be looked at again. Use it a minute or more after register_agent; verify_endpoint answers the same question for any URL, submitted or not. Read-only, no account. Returns the origin's state, its findings and the next crawl time.

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

Input Schema

NameRequiredDescriptionDefault
originYesThe origin you submitted with register_agent, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / origin / description
      Added value: +"The origin you submitted with register_agent, e.g. https://example.com"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so the safety profile is handled; the description adds value by saying no account is needed and by describing the crawl-delay timing and the fact that a next crawl time is reported. It stops short of describing response shape or pagination, but for a single-record status read that is a minor omission.

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?

Three sentences, front-loaded with the outcome enumeration and followed by usage and return-value notes; no filler. The opening sentence is somewhat run-on with nested clauses and parentheses, which costs a bit of scanability.

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

Completeness5/5

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

With only one fully documented parameter and no output schema, the description carries its weight by spelling out what the tool returns: the origin's state, its findings (listings, tools), the reason for non-listing, and the next crawl time. Nothing an agent needs in order to call it correctly is missing.

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 'origin' parameter is fully documented in the schema, including the example URL format. The description reinforces that it must be the origin previously submitted via register_agent, which is mild added meaning beyond the schema, so the baseline of 3 is appropriate.

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: reports what became of an agent submitted with register_agent, enumerating the possible outcomes (queued, crawled, not crawled) and the findings returned. It explicitly separates itself from verify_endpoint, so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit timing rule ('use it a minute or more after register_agent') and names the alternative plus the condition that selects it ('verify_endpoint answers the same question for any URL, submitted or not'). Both when-to-use and when-to-use-something-else are covered.

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.