Skip to main content
Glama
Sign In
Code Reader MCP Server

Code Reader MCP Server

by tix-ruthsan-r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_pull_requests

Retrieve pull requests for a specified service to identify API changes in PRs. Filter results by state to focus on open, closed, or all reviews.

Instructions

Get pull requests for a service to find API changes in PRs

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": {
      "serviceName": "<serviceName>"
    },
    "name": "get_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoPR state filter
serviceNameYesName of the service

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. "Get" implies a read, but nothing is said about authentication, pagination, default state behavior, rate limits, or what the returned PR records contain.

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 efficient sentence with the action front-loaded and no filler. It is terse to the point of omitting useful context, but nothing in it is wasted.

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 simple two-parameter read tool with no output schema and no annotations, the description covers the basic action but leaves the return shape, pagination, and default state semantics unstated. It is minimally viable rather than complete.

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 both parameters are already documented in the schema, establishing a baseline of 3. The description's "for a service" loosely corresponds to serviceName but adds no format, constraint, or default details beyond the schema.

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 ("Get pull requests for a service") and adds intent ("to find API changes in PRs"). However, it does not distinguish this tool from the sibling get_api_changes, which appears to cover similar ground, so an agent cannot fully route between them from the description alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_api_changes or compare_branches. The purpose phrase implies a context, but the agent must infer when this tool wins over its siblings.

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