Skip to main content
Glama

Remove or restore a counter-signal

edit_counter_signal

Before the run: the counter-signals («контрсигналы») that make a lead partial or a miss. action=remove or restore. [REST: POST /api/tasks/{id}/counter-signals/{sid}/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>",
      "signal_id": "<signal_id>",
      "action": "<action>"
    },
    "name": "edit_counter_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
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).
signal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, yet the description adds no behavioral context beyond the REST path: nothing about whether a removal is reversible, whether it needs the search to be stopped, or how concurrent web edits interact. For a mutation tool with a 'remove' branch, the missing reversibility and concurrency detail is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the resource definition comes first, which is good, but it reads as staccato notes rather than a sentence, and the bracketed REST path plus Cyrillic gloss consume space that would be better spent on behavior.

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?

No output schema exists, so the description should explain what happens after a successful call, and it does not. Combined with an undocumented signal_id and no reversibility/permission notes, the definition is thin for a non-idempotent mutation with four parameters.

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 coverage is only 50%: task_id and version are documented, but signal_id carries no description anywhere. The description only restates the action enum ('remove or restore') and adds nothing about identifying the counter-signal, so it does not compensate for the coverage gap.

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 defines the resource well ('counter-signals that make a lead partial or a miss') and names the two operations via 'action=remove or restore', but it never states the verb directly and leans on the title to say what the tool actually does. It also gives no signal for how this differs from the many edit_* siblings that mutate the same search spec.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Before the run' is the only situational hint and it is cryptic — it implies a timing constraint without explaining what 'run' means or what state the search must be in. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for related spec edits.

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