Skip to main content
Glama
Sign In

BACKLNK

by com.backlnk
OverviewDiscussionsAdmin

Mark a fix as done or skipped

update_fix_item
Idempotent

Marks one item of a BACKLNK fix queue as done (the change is made) or skipped, with an optional note. The extension's Verify re-checks the page and shows before and after.

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": {
      "queueId": "<queueId>",
      "itemId": "<itemId>",
      "state": "<state>"
    },
    "name": "update_fix_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: what was changed, or why the item was skipped (shown to the user in the extension).
stateYesdone: the change is made in the site's code; skipped: not done (say why in note).
itemIdYesThe item's id, from get_fix_queue.
queueIdYesFix queue id (fq_...), from get_fix_queue.
languageNoLanguage of the human-readable texts in the answer (summaries, findings, messages): one of en. Ids, codes and field names stay English. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-open-world behavior, and the description adds context the annotations cannot: the note is surfaced to the user in the extension, and the extension's Verify re-checks the page with before/after output, so effects are visible and re-verifiable. It does not clarify whether this tool itself applies the code change or merely records state, which keeps 'done (the change is made)' slightly ambiguous.

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?

Two tight sentences, front-loaded with the action and its scope. The Verify sentence is slightly tangential but earns its place by explaining what happens after marking.

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?

A small, fully documented mutation: required ids, enum states, and an optional bounded note are all covered by the schema, and the description supplies the user-visible consequences. No output schema exists, but the Verify sentence covers the follow-on experience, so little is missing.

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%, so the schema already documents state, note, itemId, queueId and language. The description's 'with an optional note' and 'done...or skipped' restate schema content rather than adding format, sourcing, or edge-case guidance beyond it. Baseline 3 applies.

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?

States a specific verb and resource with scope: marking ONE item of a BACKLNK fix queue as done or skipped. The parenthetical 'the change is made' disambiguates 'done', and the reference to Verify's re-check distinguishes it from the read-side siblings.

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?

Usage is implied rather than stated: mark done once the change is made, skipped when not done (say why). It gestures at the downstream Verify flow but never explicitly says when to prefer this over leaving an item unmarked or when to use verify_fixes instead. Adequate but leaves the agent to infer the workflow.

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

All BACKLNK toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources