Skip to main content
Glama

Edit, remove or restore a pain

edit_pain

Before the run: the pains («боли») the search looks for in a lead's facts. action=edit (new text of pain_id), remove, restore. [REST: POST /api/tasks/{id}/pains/{pid}/edit|remove|restore]

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": {
      "task_id": "<task_id>",
      "pain_id": "<pain_id>",
      "action": "<action>"
    },
    "name": "edit_pain"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
actionYes
pain_idYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.
versionNoThe spec version from get_search (optional: protects against an edit made meanwhile in the web).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Beyond the annotations, the description discloses that remove is reversible through restore, which is meaningful behavior for a tool annotated destructiveHint=false. It does not cover permissions, what happens if the spec is mid-run, or whether restore fails when the pain was never removed; the version-protection note lives in the schema, not the description.

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?

Very compact, with no filler. The structure is weak though: it opens with usage context rather than the operation, and the embedded REST path and bilingual gloss add tokens without helping an agent choose or call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with 40% schema coverage and no output schema, the definition is only minimally sufficient. An agent still cannot tell what state the search must be in, what remove returns, or whether text is required for action=edit.

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 40%, so the description needs to compensate. It does add the key semantic link that 'text' is the new text for pain_id when action=edit, but leaves 'version' and the interaction between action and text (e.g., ignored for remove/restore) to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('pains' the search looks for in a lead's facts) and the three operations via action=edit/remove/restore, and the title supplies the verb. However, it leads with a conceptual gloss in sentence-fragment form rather than a clear 'edit, remove or restore a pain of a search' statement, and it never distinguishes itself from siblings like edit_criterion or edit_counter_signal that operate on adjacent spec entities.

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?

'Before the run' implies the lifecycle stage at which this applies, which is useful context. There is no explicit when-not guidance, no statement of required search state or permissions, and no named alternative for editing other spec elements.

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