Skip to main content
Glama

Change the search method

set_search_strategy
Idempotent

Before the run: the search method («способ поиска») — people (search people directly), companies_first (find the companies, then the people in them), via_related_people; only the options get_search detail=spec lists for this spec. The plan and the estimate are made again. [REST: POST /api/tasks/{id}/strategy]

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>",
      "strategy": "<strategy>"
    },
    "name": "set_search_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
strategyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only but non-destructive, idempotent mutation. The description adds real value beyond them by disclosing the side effect: 'The plan and the estimate are made again,' which signals cost and downstream recomputation. It stops short of 5 because it doesn't say whether prior results are invalidated or what the response contains.

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?

The precondition 'Before the run' is correctly front-loaded and the enum explanations are useful. However, the phrasing is telegraphic and semicolon-chained, and the parenthetical Russian gloss «способ поиска» plus the trailing REST endpoint tag add little for an agent that already has the tool name and endpoint metadata.

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 three-parameter mutation with no output schema, the description covers the trigger condition, the option space, and the recomputation side effect, which is the key outcome an agent must anticipate. It could go further and state what the call returns (e.g., the refreshed plan/estimate), but nothing essential to correct invocation is missing.

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 sits at 67%, and the description compensates by defining each of the three strategy enum values in plain language, which the schema leaves as bare strings. It also contextualizes which strategies are legal per spec via get_search. The version parameter's concurrency-protection role is documented only in the schema, not echoed here.

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?

The description identifies the action (changing 'the search method') and enumerates the three concrete modes with brief explanations: people, companies_first, via_related_people. The verb itself is only implied, but the enum glosses make the effect unambiguous. It does not name a sibling it differs from, keeping it short of a 5.

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?

'Before the run' establishes a clear temporal precondition for when this tool applies, and the pointer to get_search detail=spec tells the agent where to discover which strategies are valid for a given spec. What's missing is an explicit statement of the alternative when the run has already started, the way the sibling-routing high example does.

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