Skip to main content
Glama

Manage saved search rows

spur_manage_search_table
Destructive

Reopen, delete, record signed search results into a table, or save selected rows to properties/a list for free. Create tables with spur_data_search keep_table=true. Deleting a table does not delete saved properties.

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 flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds genuinely non-obvious behavior beyond that: 'Deleting a table does not delete saved properties,' and that recorded results must be the signed payload from spur_data_search. The confirmation requirement is left to the schema's confirm field rather than restated, which is acceptable given annotation coverage.

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?

Two sentences, front-loaded with the action list and followed by two scoping caveats — no wasted setup. The phrase 'for free' is marketing-flavored noise that does not help an agent decide anything, which keeps it out of the top band.

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 four-branch tool with full schema coverage and no output schema, the description covers all four actions plus the key side-effect caveat about properties surviving table deletion. What remains thin is return behavior for the get branch and how saved rows surface afterward, but those are modest gaps against a fully documented schema.

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 baseline is 3. The description does add a little meaning by pairing each action name with its intent (reopen/delete/record/save to properties or a list), but it does not clarify the save branch's row_ids vs. all vs. list_id choice, or the get branch's filter parameters, beyond what the schema already says.

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 concrete verb list tied to the tool's four action branches: 'Reopen, delete, record signed search results into a table, or save selected rows to properties/a list.' That maps cleanly onto the get/delete/record_rows/save variants in the schema, so an agent knows what the tool does. It stops short of naming which sibling handles plain searching versus table listing, 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?

It gives one explicit routing hint: 'Create tables with spur_data_search keep_table=true,' which usefully tells the agent this tool is not for table creation. However, it never says when to choose this over spur_list_search_tables, spur_control_table_run, or spur_run_table_column, and gives no prerequisite or ordering guidance for the delete and save actions.

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