Skip to main content
Glama

ecosystem_apply_debate_result

Submit a debate conclusion to move a deep review to the debated stage, recording risks, learnings, or integration notes and a recommendation.

Instructions

Stage 2 writeback — submit debate conclusion to advance to debated.

At least one of risks_md / learnings_md / integration_md must be non-empty. integration_recommendation is a short enum: integrate / reference / learn / skip.

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": {
      "deep_review_id": "<deep_review_id>"
    },
    "name": "ecosystem_apply_debate_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional agent identifier recorded on the review.
risks_mdNorisk points markdown.
learnings_mdNopoints-to-learn-from markdown.
deep_review_idYesTarget deep_review row id.
integration_mdNointegration suggestions markdown.
integration_recommendationNointegrate/reference/learn/skip enum.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A3.8/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 behavioral burden; it does disclose the mutation's effect (state moves to `debated`) and a validation rule, which is real value. It does not say whether existing risks/learnings/integration content is overwritten, whether the call is idempotent or repeatable after the state transition, or what permissions are needed for a write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses, front-loaded with the stage and effect, then the hard precondition, then the enum. Nothing is decorative and the validation rule is placed where an agent will see it before constructing arguments.

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?

An output schema exists and parameter coverage is complete, so return values and field meanings need no explanation. However, for an unannotated write tool it omits the surrounding state machine: what state the deep review must already be in, whether re-invocation is allowed, and what happens on validation failure.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds a genuine cross-parameter constraint the schema does not encode: at least one of risks_md / learnings_md / integration_md must be non-empty. It also restates the integration_recommendation enum, which is slightly redundant with the schema but reinforces the allowed set.

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?

States a specific verb and resource ('submit debate conclusion') plus the concrete effect ('advance to ``debated``'), which is more than a restatement of the name. 'Stage 2 writeback' places it in a pipeline, which distinguishes it from earlier-stage siblings like ecosystem_claim_shallow, though it never names an alternative 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?

The 'Stage 2' label and the 'advance to debated' target give clear context for when this tool is the right call, and the 'at least one of ... must be non-empty' line reads as a precondition. It stops short of naming alternatives or stating exclusions (e.g., what to do if the review is not yet at stage 1).

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

Deploy Server

Other Tools