Skip to main content
Glama

List application pull request reviews

list_application_pull_request_reviews
Read-only

List the AI reviews Ankra has already posted on an Application's pull requests, newest first, with each review's findings. Use it to see what the reviewer actually said before changing its configuration, and to tell 'the lane is off' apart from 'the lane ran and found nothing'. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "list_application_pull_request_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many reviews to return, newest first. Defaults to 10.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint is already declared, and the trailing 'Read-only.' merely restates it. What the description genuinely adds beyond annotations is the result ordering (newest first) and the interpretive hint that an empty result can mean 'the lane ran and found nothing' — useful, but it omits pagination/truncation behaviour and what fields a review finding actually contains.

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 sentences, front-loaded with the scope and followed by usage rationale; little waste. The closing 'Read-only.' is redundant with the readOnlyHint annotation and slightly dilutes an otherwise tight definition.

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?

For a simple two-parameter read tool with no output schema, this covers scope, ordering, and intent adequately. The one real gap is the shape of a 'review' and its findings, which an agent cannot infer from schema or annotations since no output schema exists.

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%: both application_id and limit are documented in the schema, including the default of 10 and the max of 20. The description only echoes the 'newest first' ordering already present in the limit description, so it adds little semantic value beyond the structured fields. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (List) and a precisely scoped resource (AI reviews Ankra has already posted on an Application's pull requests), plus ordering and payload (newest first, with each review's findings). This scope is distinct from neighbouring tools like get_application_ai_config or github_get_pull_request, so an agent can pick it without opening the schema.

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?

It gives a concrete decision context: 'see what the reviewer actually said before changing its configuration', plus a diagnostic use case for distinguishing an inactive lane from a lane that ran clean. It stops short of naming an explicit alternative tool or stating when not to call it, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.