Skip to main content
Glama

Rename a search

rename_search
Idempotent

The name a search card shows (1-80 characters). [REST: PUT /api/tasks/{id}/title]

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>",
      "title": "<title>"
    },
    "name": "rename_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered without the text. The description adds only the 1-80 character limit, which is already in the schema, plus a REST path reference that conveys no additional agent-relevant behavior.

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 a single short sentence with no filler, but the structure is backwards: a parameter definition occupies the entire description while the operation itself is relegated to a bracketed REST note. It is terse rather than efficiently front-loaded.

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

Completeness2/5

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

For a simple two-parameter mutation with annotations and no output schema, the description still omits the core statement of what changes and whether the rename is reversible or affects running searches. An agent could call it, but only by trusting the title and REST hint.

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 50%: task_id is documented in the schema, but title has no schema description. The description does supply the meaning of title (the displayed card name) and its length bound, which fills the documented gap, though it gives no format or validation detail beyond that.

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

Purpose2/5

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

The description reads as a parameter gloss ("The name a search card shows") rather than stating the action, so the verb must be inferred from the tool title and the bracketed REST line "PUT /api/tasks/{id}/title". It never says outright that this renames a search, and it offers no differentiation from siblings like edit_search_spec or revise_search.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as edit_search_spec for broader search modifications. The agent must guess that this is the narrow title-only mutation.

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