Skip to main content
Glama

PebbleLaunch

Check a submission

check_status

Status of a submission you made (needs its id + status_key). While ownership is pending this re-checks the proof (at most once a minute). Set resend_email to re-send the maker's confirmation link.

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>",
      "status_key": "<status_key>"
    },
    "name": "check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
status_keyYes
resend_emailNo

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?

Annotations only say readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description adds the non-obvious behavior that the call re-checks the proof while ownership is pending, throttled to once a minute, and that resend_email sends an actual email. That explains the non-read-only side effect rather than leaving it to inference, though it doesn't say what states the status can be in.

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?

Two tight sentences, front-loaded with the core purpose, then the ownership/throttling caveat, then the optional parameter's effect. Slightly compressed phrasing ("needs its id + status_key") but no wasted text.

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?

There is no output schema, so the description is the only place a caller could learn what "status" values come back or what to do with them; it never says. It covers the side effects and the throttling well, but for a polling-style status tool the missing return-value framing is a real gap.

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 0% schema description coverage, the description must carry all parameter meaning. It clarifies resend_email (re-sends the maker's confirmation link) and that id and status_key are both required, but it never explains what status_key is, where it comes from, or why it is needed alongside id — the most opaque parameter is left undefined.

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?

"Status of a submission you made" names a specific verb (check/retrieve status) and resource (a submission), and the ownership/resend details signal this is the follow-up to submit_product. It is clearly differentiable from the launch-reading siblings, though it never explicitly names an alternative.

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?

The description implies usage (check after submitting, pass the id and status_key you received), and it explains the narrow condition under which re-checking happens (ownership pending, at most once a minute). But there is no explicit "use this when..." statement and no guidance on what to do if the status_key is lost or the submission is already confirmed.

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