Skip to main content
Glama
Sign In
fixgraph

fixgraph

by jawdat6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fixgraph_get_fixes

Retrieve all verified fixes for a FixGraph issue using its ID or slug.

Instructions

Get all verified fixes for a specific FixGraph issue by its ID or slug.

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": "fixgraph_get_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesIssue ID or slug from a fixgraph_search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removedv1.0.1
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears full transparency burden. It only states 'get all verified fixes'—a read operation with no mention of side effects, authentication, rate limits, or limitations, which is insufficient for full disclosure.

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?

One sentence, 14 words, front-loaded with verb and resource. Every word earns its place. No wasted text.

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 1-parameter tool with no output schema, the description is adequate. It covers the essential purpose and input. Could be enhanced by briefly noting that an empty list is returned if no fixes exist, but this is minor.

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% with clear parameter description. The tool description adds 'by its ID or slug' but does not enrich beyond the schema's description. Baseline 3 is appropriate as schema already does the heavy lifting.

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?

'Get all verified fixes for a specific FixGraph issue by its ID or slug' clearly states the verb (get), resource (verified fixes), and input (ID/slug). It naturally distinguishes from siblings: fixgraph_search finds issues, fixgraph_submit_fix sends fixes.

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?

The description implies usage (after obtaining an issue ID from search) but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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