Skip to main content
Glama

fix_and_resolve

Apply a code fix to resolve a pinned annotation, recording the commit, branch, or PR for traceability and removing it from stakeholder view.

Instructions

Resolve a pin after applying a code fix. Transitions the pin directly to "resolved" status so it disappears from the stakeholder view. No thread comment is added — the commit is the record of the fix. Pass commitSha (from git rev-parse HEAD), branchName (git branch --show-current), and prUrl (from gh pr view --json url -q .url if a PR was opened) so the Pincushion dashboard can link the pin to the implementing commit, branch, and PR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prUrlNoOptional pull request URL (GitHub/GitLab/Bitbucket). Validated against PR-URL shape before storage. Surfaces as a clickable "Resolved in PR #N" link on the pin.
filePathNoOptional file path where the fix was made
commitShaNoOptional git commit SHA that implemented the fix. Stored on the annotation for bidirectional pin↔commit traceability when the project has recordCommitSha enabled (default: true).
branchNameNoOptional branch name the fix was implemented on. Surfaces on the pin in the dashboard so stakeholders can see where the change shipped.
lineNumberNoOptional line number of the fix
annotationIdYesThe annotation ID to fix
fixDescriptionYesDescription of the fix applied (e.g. "Updated button label to match design spec")
Behavior4/5

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

Discloses key behaviors: transitions to 'resolved' status, disappears from stakeholder view, no thread comment added, and commit linking. No annotations provided, so description carries full burden; it covers major effects but omits potential side effects or reversibility.

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?

Highly concise: three sentences packed with purpose, behavior, and parameter derivation instructions. No wasted words, front-loaded with essential information.

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?

Given 7 parameters and no output schema, the description adequately covers purpose, behavior, and parameter usage. Lacks return value details, but tool likely returns a success/error status implicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds meaningful context for commitSha, branchName, prUrl (e.g., shell commands to derive values). For other params, it restates schema descriptions but adds linking behavior context.

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 clearly states the verb 'resolve' and the resource 'a pin after applying a code fix'. It differentiates from siblings like 'resolve_annotation' by emphasizing the post-fix scenario and the lack of a thread comment.

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?

Provides explicit context on when to use (after a code fix) and instructions for populating commitSha, branchName, prUrl. However, it does not explicitly state when not to use or compare to alternatives like 'resolve_annotation'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jcooley8/pincushion-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server