Skip to main content
Glama
Sign In
preset-mcp

preset-mcp

by Evan-Kim2028
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_saved_query

Retrieve details of a saved query by providing its ID, with options for compact, standard, or full response.

Instructions

Get detail for a single saved query.

Args: query_id: The saved query ID. response_mode: 'compact', 'standard', or 'full'.

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": {
      "query_id": "<query_id>"
    },
    "name": "get_saved_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
query_idYes
response_modeNostandard

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. The description states a read operation ('get') but does not explicitly confirm non-destructiveness or disclose potential behaviors like error handling, authorization needs, or side effects. The output schema helps but transparency is minimal beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence plus two parameter lines—no redundancy, front-loaded with purpose. Every sentence contributes value.

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?

Given the presence of an output schema covering return values, the description covers the essential purpose and parameters. It lacks mention of potential errors (e.g., invalid query_id) or dependencies on other tools, but these are minor omissions for a simple getter.

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?

The description adds meaning by explaining query_id as 'The saved query ID' and enumerating response_mode options ('compact', 'standard', 'full'). This compensates for the schema having no parameter descriptions (0% coverage). However, it could elaborate on differences between response modes.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Get detail for a single saved query.' The verb 'get' and resource 'detail for a single saved query' are specific and distinguish from siblings like list_saved_queries (list overview) and create/update/delete operations.

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?

The description implies usage for retrieving details of a specific saved query but offers no explicit guidance on when to use this tool versus alternatives (e.g., list_saved_queries) or when not to use it. No prerequisites or context are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools