Skip to main content
Glama
Sign In
Review Helper

Review Helper

by antoinebou12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Read feature section

read_section
Read-onlyIdempotent

Retrieve one feature section's original patches and provider comments from a review snapshot to review changes by feature rather than by file.

Instructions

Read only one feature section's original patches and provider comments.

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>",
      "section_id": "<section_id>"
    },
    "name": "read_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYesReview snapshot ID returned by open_review.
section_idYesSection ID from the compact review index.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that returned content is original patches plus provider comments, but says nothing about size, pagination, or whether comments are inline versus threaded. With annotations carrying the main burden, a 3 is appropriate.

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?

A single short sentence with no wasted words, front-loading the verb and the scoping constraint. It is perhaps too terse to be maximally useful, but nothing is redundant.

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 two-parameter read tool with full annotation coverage and full schema descriptions, the description covers the essentials. It nonetheless omits what a section response contains in structure and whether large sections are truncated, which an agent would want before calling.

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 coverage is 100% and each parameter already documents its provenance (review_id from open_review, section_id from the compact review index). The description adds no format or constraint detail beyond that, so it sits at the baseline of 3.

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: reading one feature section's original patches and provider comments. The word "only" enforces single-section scope, distinguishing it from a whole-review fetch, though no sibling is named explicitly even though open_review is the likely bulk alternative.

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?

Usage is implied — you fetch a single section after holding a review_id from open_review and a section_id from the compact review index. There is no explicit when-to-use or when-to-avoid statement, and no pointer to an alternative for reading multiple sections; the guidance is inferable but not spelled out.

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