OpenInvest

committee_review

Read-onlyIdempotent

Retrieve the unchanged original transcript and issued verification packet for a previously submitted draft by context_id to review or audit the analysis without completing work.

Instructions

Retrieve unchanged original transcript and issued verification packet; never completes work.

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": {
      "context_id": "<context_id>"
    },
    "name": "committee_review"
  }
}

Input Schema

Name	Required	Description	Default
`context_id`	Yes	Exact context_id for this ledger's previously submitted draft.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.68.10Nov 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful context beyond them by specifying that the transcript is 'unchanged' and that the tool 'never completes work,' clarifying that retrieval has no workflow side effect. It does not discuss permissions or latency, but those are not central for this simple read operation.

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 a single front-loaded sentence with no filler, and it puts the retrieval action before the behavioral caveat. The semicolon structure keeps the non-completion note compact, though the phrase 'never completes work' is slightly cryptic.

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 one fully documented parameter, rich annotations, and an output schema, the description supplies enough to call the tool correctly and understand that it is an unchanged read. It could be stronger by linking the retrieval to the committee review workflow after a draft is submitted, but it is adequate for this simple tool.

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?

The single context_id parameter has 100% schema description coverage, including the exact meaning ('previously submitted draft'). The description adds no further parameter-level syntax or constraints, so the schema is doing the work.

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 uses a specific verb ('Retrieve') and names two concrete artifacts ('unchanged original transcript' and 'issued verification packet'), so the agent knows what comes back. It also signals what it does not do ('never completes work'), which separates it from completion-oriented siblings such as submit_committee, though it does not explicitly name them.

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 statement of when to choose this tool over prepare_committee, run_committee, or submit_committee. The phrase 'never completes work' implies it is not the completion step, but the description leaves the triggering condition and alternatives to inference.

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