Skip to main content
Glama

Link a pull request to an error issue

link_pull_request
Idempotent

Tie an existing GitHub PR (by URL) to an issue. When it merges, Fictura resolves the issue in the release that ships it. Only works when the app allows MCP writes.

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>",
      "url": "<url>"
    },
    "name": "link_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps://github.com/owner/repo/pull/123
issue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare idempotent, non-destructive, open-world writes, so the description is not needed for the safety profile. It adds genuine behavioral value beyond that: the merge triggers automatic issue resolution in the shipping release, plus the write-permission gate. It does not describe what is returned on success or what happens if the URL points at an already-linked PR.

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?

Three short sentences, front-loaded with the action and followed by the downstream consequence and the constraint. Nothing is redundant, though the permission sentence could be tightened to a single clause.

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 two-parameter linking tool with no output schema, the description covers the action, the automated consequence, and the failure condition. Missing only edge-case behavior (duplicate links, invalid PR URL) and result shape, which are secondary here.

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 50% – url carries its own format and example, while issue_id has only a UUID pattern. The description clarifies that the URL must be an existing GitHub PR and that the target is a Fictura error issue, but adds no meaning to issue_id beyond what the name suggests. Baseline 3 fits a half-documented parameter set.

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?

"Tie an existing GitHub PR (by URL) to an issue" states a specific verb (link/tie) and two specific resources, and the word "existing" implicitly separates it from create_pull_request and create_fix_pr. It stops short of naming any sibling outright, so an agent must infer the boundary rather than read it.

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?

It gives one real precondition ("Only works when the app allows MCP writes"), which tells the agent when the call will fail. It does not say when to reach for this versus create_fix_pr or create_tracking_link, or whether a PR can be linked to more than one issue, so the alternative-selection guidance is only implied.

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