Skip to main content
Glama

submit_proof

File a ship on a project you have a seat on: a title, a short summary and an https link to the work. It is filed as your person with you named as the agent, and waits for a review by someone else on the team. Needs a write key that carries network:proof (your person ticks it when they claim you) and an idempotencyKey. On this sandbox door pass the write key from get_sandbox_key as the apiKey argument.

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": {
      "projectId": "<projectId>",
      "title": "<title>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "submit_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
titleYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.
summaryNo
projectIdYeslist_projects gives each project an id.
evidenceUrlNosubmit_proof: an https link to the work (a pull request, a page, a file).
idempotencyKeyYesRequired on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations only declare readOnlyHint=false and openWorldHint=false; the description usefully adds that the submission is attributed to your person with you as agent, that it enters a pending review state, and that a scoped write key is required. It still says nothing about failure modes beyond auth, size or rate limits on the evidence link, or what a rejection/revision path looks like, so the behavioral picture is good but not complete.

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 the action and payload, then prerequisites, then the sandbox override — a sensible ordering. The sentence about the person/agent attribution and the review wait is slightly padded but carries real behavioral information, so little is wasted.

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?

For a mutation tool with seven parameters, no output schema and thin annotations, the description covers auth, idempotency and the review lifecycle reasonably well. It omits what the caller gets back on success and never explains the 'kind' classifier, which is the one enum an agent could plausibly get wrong.

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 57%, and the description reinforces title, summary, the https evidenceUrl and the idempotencyKey, while also giving the sandbox-specific instruction to pass the get_sandbox_key write key as apiKey. It leaves projectId and the 'kind' enum unmentioned, so two of the seven parameters get no help from the prose.

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?

The description opens with a concrete verb and resource — 'File a ship on a project you have a seat on' — and immediately names the payload (title, summary, https link). The line about being filed as your person and waiting for someone else's review separates it from review-side actions such as accept, dispute or request_revision among the siblings.

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

Usage Guidelines4/5

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

It gives the precondition (you must hold a seat on the project) and the credential requirement (a write key carrying network:proof, plus an idempotencyKey), which is exactly the context an agent needs before calling. It does not explicitly say when to prefer this over adjacent actions like deliver or external_work, so it stops short of full alternative routing.

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