Skip to main content
Glama

Ask Fictura's AI to fix an error issue

start_fix_run

Start a hosted fix run: Fictura's AI finds the root cause and, if allowed, opens a draft PR. It spends the app's own Anthropic money, capped per run and per day. Poll get_fix_run. Needs MCP writes and AI fixes on.

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

Input Schema

NameRequiredDescriptionDefault
stop_atNo
issue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already mark this as a non-read-only, open-world, non-idempotent, non-destructive call, but the description adds the details an agent cannot get from them: the run spends the app's own Anthropic credits, those credits are capped per run and per day, and a draft PR appears only 'if allowed'. A statement about what a repeat call does is still missing, but the cost and permission behavior is well covered.

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?

Four short sentences; the action and outcome come first, then the cost warning, then the polling instruction, and then the prerequisites. No sentence is wasted, and the key constraints appear up front.

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 definition still tells the agent that results come from get_fix_run and that prerequisites must be satisfied before the call. The one real gap is that 'stop_at' is never translated into behavior, which matters for a tool whose whole point is staged stopping.

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

Parameters2/5

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

Schema description coverage is 0%, so the description has to define both parameters, and it does not. The 'issue_id' meaning is only implied, and the 'stop_at' enum (root_cause, plan, pr) is never explained, even though 'finds the root cause and, if allowed, opens a draft PR' is the only hint that the run stops at different points.

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?

It gives a specific verb-plus-resource ('Start a hosted fix run') and immediately explains what the run does: find the root cause and optionally open a draft PR. An agent can tell it apart from create_fix_pr and get_fix_run, because this is the entry point that starts the work rather than creating the PR or polling for status.

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?

The definition states the prerequisites ('Needs MCP writes and AI fixes on') and the next step ('Poll get_fix_run'), which is enough to use it correctly. It does not, however, say when not to use it, or when to choose create_fix_pr or another path instead.

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