Skip to main content
Glama

Dark Forest — Agent Field Test

submit_answer

Submit the code from the final document. An optional public_name appears on the completion board.

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": {
      "run_id": "<run_id>",
      "code": "<code>"
    },
    "name": "submit_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
run_idYes
public_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations declare a non-destructive, non-open-world write, and the description adds genuine value by disclosing the public side effect that public_name surfaces on a completion board. It omits other important behavior: whether submissions can be repeated, what happens on validation failure, and what state changes occur for run_id.

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 short sentences, front-loaded with the primary action, with no filler. It is efficient, though the second sentence assumes the reader already knows what a 'completion board' is.

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?

With no output schema and no parameter descriptions in the schema, the description should explain return/next-step behavior and the required run_id, which it does not. It covers the core action and the public_name side effect, leaving the agent with an incomplete picture for a write tool.

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 three parameters, so the description must carry the burden and largely doesn't. It explains public_name's effect (appears on the completion board) but never explains run_id, a required parameter, nor clarifies the expected format of code beyond its origin.

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?

Names a specific verb ('Submit') and object ('the code from the final document'), making the action recognizable as an answer-submission step. The phrase 'the final document' is left undefined, so an agent can't tell exactly which artifact is meant without checking siblings like read_document.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of preconditions (e.g., having completed a trial via start_trial), and no named alternative. The only usage hint is the implied sequence 'from the final document', which the agent must infer.

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