Create a reusable query preset by specifying name, query type, and filters to quickly apply saved filters to future searches.
Save a reusable query preset.
[Category: Query & Search] [Auth: none]
[Related: list_query_presets, run_query_preset, delete_query_preset]| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| query_type | Yes | ||
| filters | Yes | ||
| description | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description only mentions 'Auth: none'. It does not disclose behavioral traits like overwrite behavior, side effects, or limitations. With no annotations, the description carries full burden but provides minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and to the point, with the purpose clearly stated upfront. Related tools are listed efficiently. However, it could be improved by adding more detail without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 4 parameters with no schema descriptions, no output schema, and a write operation, the description is sparse. It does not explain what happens on success/failure, return values, or constraints like naming conventions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameter descriptions in the input schema (0% coverage). The description does not add any meaning or examples for the parameters, leaving the agent to guess their exact expected format or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Save' and the resource 'query preset', and includes a category and related tools that help distinguish it from siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Related tools are listed, but no explicit guidance on when to use this tool versus alternatives, or any prerequisites. The context is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KpihX/tick-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server