Skip to main content
Glama

Manage search automation

spur_manage_search_automation
Destructive

Get full settings, update/enable/disable, delete, or preview/apply migration to Data Search. Updating an enabled automation or applying migration needs approval because subsequent runs can spend/contact people. Disable is immediate.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely non-obvious behavior: that updates to an enabled automation and migration application require user approval because subsequent runs can spend credits or contact people, and that disable takes effect immediately. This is exactly the extra context annotations cannot carry. It does not mention that delete is irreversible or that migration defaults to a dry run, leaving some gaps.

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?

Three short sentences, front-loaded with the action enumeration before the safety caveats, with no filler. The phrasing is compressed to the point of terseness in places ('preview/apply migration to Data Search'), but every sentence carries operational information.

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 multi-action lifecycle tool with an annotation set covering the destructive/open-world profile and a fully-described input schema, the description covers actions, approval gating, and immediacy of disable adequately, and no output schema needs explaining. The main holes are the unfulfilled 'see the tool description' pointer for the events list and the absence of any note that delete is permanent.

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 description coverage is 100%, so the per-action oneOf branches, the confirm constraint, and the large changes object are already documented in-schema, making 3 the baseline. The description clarifies the preview/apply distinction for migration but says nothing about the confirm flag, dry_run, or the changes payload. Notably, the 'events' field tells the reader to 'see the tool description,' yet the description never discusses events at all, leaving that pointer unfulfilled.

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 opens with a compact enumeration of the concrete operations (get settings, update/enable/disable, delete, preview/apply migration) against the named resource 'search automation' / Data Search. An agent can immediately tell this is the settings-lifecycle tool rather than the create (spur_create_search_automation) or run (spur_run_search_automation) siblings. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

Usage context is implied through the action list plus the approval rule (updating an enabled automation or applying migration needs approval; disable is immediate), which tells the agent which actions are cheap versus gated. However, it never says when to use this tool versus spur_run_search_automation, spur_list_search_automations, or spur_manage_search_table, and offers no exclusions. The agent can infer the lifecycle role but must reason about it.

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