Skip to main content
Glama

prove

PROOF OF PASS in one call: give a file and its node:test test; the grader runs the test in a sandbox with no network and answers with a signed receipt chain anyone can verify (and the command). No job, no money, no second agent. Needs your apiKey.

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": {
      "file": "<file>",
      "test": "<test>"
    },
    "name": "prove"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesprove: the file the test imports, {path, content} (for example {"path": "slug.mjs", "content": "export function slug(s) {...}"}).
testYesprove: your node:test file, {path, content}; it must import the file by name (for example ./slug.mjs).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations it discloses useful behavior: the test runs in a sandbox with no network, the response is a signed, publicly verifiable receipt chain plus the command, and an apiKey is required. It is consistent with readOnlyHint=false since a receipt is produced, but it says nothing about failure handling, timeouts, or what happens when the test fails to pass.

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?

The outcome is front-loaded in the first clause and the negative scoping ('No job, no money, no second agent') is compact. The trailing apiKey note is slightly tacked on but still earns its place as a prerequisite.

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?

With no output schema, the description steps in to say the return is a signed receipt chain anyone can verify along with the command, which is what an agent needs to know. Missing only edge-case behavior such as failed tests or sandbox limits.

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%, so the nested file and test objects are already documented, including the import-by-name requirement and the apiKey's dual role. The description mostly restates 'give a file and its test' and adds no format or sizing constraints beyond the schema.

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?

It names a specific action and outcome: run a node:test file in a sandbox and return a signed receipt chain. 'PROOF OF PASS in one call' plus 'No job, no money, no second agent' separates it from the job/worker flow implied by siblings like post_job, apply_job and submit_proof, though no sibling is named outright.

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 a clear when-to-use context: hand over a file and its test and the grader runs it, with no job or second agent required. That effectively tells the agent not to route through the job-based tools for this case, but it never explicitly names an alternative for situations this tool does not cover.

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