Skip to main content
Glama

Apply criteria changes (spends credits)

revise_search

Applies chosen proposals of diagnose_search. SPENDS CREDITS: show the price of that combination and pass it as confirm_credits after the user's yes, with the diagnosis' version. For a finished search whose people ran out, more (and stop_at_target) say how many more leads to find with the changes. [REST: POST /api/tasks/{id}/revise]

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>",
      "accept": "<accept>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "revise_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
moreNo
acceptYes
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).
stop_at_targetNo
confirm_creditsYesThe price in credits the matching quote returned, shown to the user and confirmed by them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say this is a non-readonly, non-destructive, non-idempotent mutation; the description adds the material facts: it SPENDS CREDITS, the cost must be quoted to and confirmed by the user, and `version` protects against a concurrent web edit. That is exactly the kind of side-effect and concurrency disclosure annotations cannot convey.

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?

The credit-spend warning is front-loaded in caps right where an agent will see it, and the sentences are dense with actionable content. The trailing bracketed REST endpoint is minor noise that does not help tool selection.

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 credit-spending mutation with no output schema, the definition covers cost, user confirmation, and optimistic concurrency. It leaves open what actually happens to existing leads and results after the revision (whether the search re-runs and whether the `more` leads arrive immediately), which an agent committing credits would reasonably want to know.

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

Parameters4/5

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

Schema coverage is 50%, so the description must carry weight and mostly does: it defines confirm_credits as the quoted price shown to and approved by the user, explains version as coming from the diagnosis, and clarifies that `more` plus stop_at_target control how many additional leads to find. `accept` is only implied ("chosen proposals of diagnose_search") — it never states the array holds proposal identifiers, nor the 1–10 item limits — which keeps it below 5.

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

Purpose4/5

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

States a specific verb and resource — applies selected proposals produced by diagnose_search — and names the sibling whose output it consumes. An agent can tell this is the commit step after diagnosis, though it never explicitly contrasts itself with edit_search_spec or run_search, which are the nearest ambiguous alternatives.

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?

Gives concrete sequencing rules: show the price of the combination, get the user's yes, then pass that price as confirm_credits together with the diagnosis' version. It also carves out a specific scenario (finished search whose people ran out → use `more` and stop_at_target). It lacks explicit when-not guidance and never says how this differs from editing the spec directly.

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