Skip to main content
Glama

List saved searches

spur_list_search_tables
Read-onlyIdempotent

Reopen saved search tables from the app or MCP. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spur_list_search_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return
offsetNoNumber of items to skip, for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only two facts beyond that: the listing spans tables created either in the app or via MCP, and the operation is 'Free' (a cost note). It says nothing about ordering, defaults, or result shape.

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 short sentences with no padding, and the resource identification comes first. The word 'Free' is marginal value and 'Reopen' is imprecise, but there is no wasted structure.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and rich annotations, this is nearly sufficient, but with no output schema the description should explain what a 'search table' entry contains and in what order results come back. 'Reopen' also leaves the read semantics ambiguous.

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% for both limit and offset, including defaults and ranges, so the schema fully documents the parameters. The description adds no meaning about pagination behavior or sensible limit values, so the baseline of 3 applies.

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

Purpose3/5

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

The phrase 'saved search tables' names the resource, but the verb 'Reopen' does not clearly convey a list/retrieval operation and could be misread as opening or mutating something. The title ('List saved searches') carries most of the clarity, and the description itself gives no indication of scope or what the returned items are.

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 guidance on when to use this tool versus siblings such as spur_list_search_automations, spur_manage_search_table, or spur_data_search. 'From the app or MCP' hints at source coverage but is not a when-to-use rule, and no exclusions are stated.

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