Pay With Prompt

submit_answer

Answer one prompt with the agent key. A pass pays that prompt once.

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": {
      "prompt_id": "<prompt_id>",
      "answer": "<answer>"
    },
    "name": "submit_answer"
  }
}

Input Schema

Name	Required	Description	Default
`answer`	Yes
`prompt_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

C2.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two important behavioral traits: the agent key is required, and a 'pass' pays the prompt once. However, it does not explain side effects, idempotency, failure modes, or what exactly a 'pass' is.

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 description is two short sentences and front-loads the core action. The second sentence is vague, but the overall structure is efficient with little wasted wording.

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

Completeness2/5

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

This is a mutating submission tool with no annotations, no output schema, and 0% schema description coverage. The description omits return behavior, error handling, idempotency, and the meaning of the payment-like 'pass', leaving substantial gaps for an agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two required parameters. The description mentions 'prompt' and 'answer' in passing, but it does not explain the expected format of prompt_id, what constitutes a valid answer, or any constraints on either parameter.

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 states a specific verb and resource: answer one prompt. It also names the agent key context and a payment-like effect, distinguishing it from siblings such as list_prompts or get_balance. The phrase 'A pass pays that prompt once' is somewhat cryptic, but the core action is clear.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, no prerequisites, and no conditions for choosing this over alternatives. It implies that it submits an answer to one prompt, but it does not clarify whether this is for open prompts, paid prompts, or specific agent states.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pay With Prompt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?