Skip to main content
Glama
Sign In
mcp-devils-advocate

mcp-devils-advocate

by AleBrito124356
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_verdict

Compile a completed review into a final verdict report once all phases finish, including claim, phase items, risk score, and deterministic assessment.

Instructions

Compile the final report for a completed review.

Only available once every phase is complete — otherwise it raises an error saying what is still missing. The report contains the claim, all items organized by phase (with rebuttals/mitigations/tests/responses attached to their targets), an aggregate risk score, and a deterministic assessment: "claim survives scrutiny", "claim needs revision", or "claim refuted" (rules documented in assessment_reason). Gauntlet reviews also include one sub-verdict per lens under 'lenses'.

Args: review_id: The review session id (e.g. "rev-x9k2").

Returns: dict — the compiled verdict report.

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": {
      "review_id": "<review_id>"
    },
    "name": "get_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the blocking precondition, the error behavior, and the exact report contents (claims, phases, attached rebuttals/tests, aggregate risk score, deterministic assessment plus gauntlet lenses). It stops short of stating whether the call mutates state or is purely read-only, but the 'compile report' framing implies a read.

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?

Well front-loaded: the action and the precondition come first, then report contents, with Args/Returns separated. The multi-line detail about report structure is dense but each element describes a concrete part of the output, so it largely earns its place.

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?

No output schema exists, and the description compensates by enumerating the returned report's structure and possible assessment strings. Combined with the precondition and error disclosure, an agent has what it needs to invoke and interpret the call.

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 0%, so the description must compensate, and it does: it explains review_id as the review session id and supplies a concrete example format ("rev-x9k2"). That is useful beyond the bare string type, though it is a single simple 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?

States a specific verb (Compile) and resource (final report/verdict) and scopes it to a completed review, which is meaningfully more specific than the bare name 'get_verdict'. It does not explicitly distinguish itself from the sibling export_report, so it falls short of a 5.

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?

Gives a clear precondition ("Only available once every phase is complete") and describes what happens if that is violated, which tells the agent when this tool is callable. It stops short of routing between siblings like export_report vs get_review.

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