Skip to main content
Glama

Pull requests for an error issue

get_pull_request_status
Read-only

The PRs tied to an issue (opened by Fictura or linked), with state, draft, CI checks, merge and the release that shipped it.

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": {
      "issue_id": "<issue_id>"
    },
    "name": "get_pull_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful scoping detail that only PRs opened by Fictura or linked to the issue are included, plus the fields returned, but says nothing about pagination, ordering, or behavior when no PRs exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource front-loaded and every clause contributing either scope or return-field information. There is no filler or repetition of the title.

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 no output schema, the description usefully enumerates the returned PR attributes and the inclusion rule. For a one-parameter read tool that is nearly complete; only pagination and empty-result handling are unaddressed.

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?

There is one parameter with 0% schema description coverage, but issue_id is a self-describing UUID and the description's 'tied to an issue' phrasing confirms its scoping role. No additional format or lookup guidance is provided, so the description does not compensate for the coverage gap but the single obvious parameter keeps this adequate.

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 names the resource (pull requests tied to an issue) and enumerates the returned attributes (state, draft, CI checks, merge, release). It implicitly distinguishes itself from link_pull_request and create_pull_request by being a read, but does not name those siblings explicitly.

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 when-to-use or when-not guidance, and no alternatives are named. The agent must infer from the name that this is the read path for an issue's PRs versus linking or creating one.

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.

Resources