Skip to main content
Glama

review_proposals

Inspect pending protocol proposals to view validation results, risk scores, and recommendations for approval decisions.

Instructions

Review pending protocol proposals. Shows validation results, risk scores, and recommendations.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "review_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum proposals to return (default: 10)
sourceNoFilter by source
statusNoFilter by status (default: pending)
projectDirYesAbsolute path to the project directory
proposalIdNoGet details for a specific proposal
includeStatsNoInclude proposal statistics (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the substance of the response (validation results, risk scores, recommendations) for a tool with no output schema, but it never states that the operation is read-only, which matters given a similarly named run_review sibling.

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 action and immediately followed by what the caller gets back; nothing is padded. The only minor inefficiency is that 'pending' duplicates and slightly contradicts the schema's default status filter.

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?

For a 6-parameter read tool with no annotations and no output schema, the description covers intent and return contents adequately but omits the filtering model (status/source/limit), the stats option, and any read-only assurance. Enough to call it, not enough to call it confidently.

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?

Schema description coverage is 100%, so every parameter including the status/source enums and the limit bound is already documented in the schema. The description adds no filtering, scope, or format detail beyond that, so the baseline of 3 applies.

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?

Uses a specific verb+resource ('Review pending protocol proposals') and adds what the response contains (validation results, risk scores, recommendations). It does not distinguish itself from nearby siblings such as run_review, check_reviews, or get_review_results, and the verb 'Review' alone leaves read-vs-execute ambiguous.

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

Usage Guidelines3/5

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

Scope is implied ('pending protocol proposals'), but there is no explicit when-to-use statement, no exclusions, and no pointer to the alternative tools that also deal with reviews or approvals. The word 'pending' also understates that the schema lets the caller filter to any status.

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