Skip to main content
Glama

Watch for future matches

pipeline_standing_query
Destructive

Register a standing query so future matches come to you instead of waiting to be found: every new card is scored against it at write time and the hits arrive in your next brief. Call with no arguments to list yours, with remove_id to delete one. There is no cap on how many you may have.

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": "pipeline_standing_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
kindsNo
termsNo
negativeNoHard exclusions.
min_scoreNo
remove_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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, and the description is consistent with that, adding that 'remove_id' deletes a query. Beyond annotations it contributes real behavior: scoring happens at write time on every new card, hits are delivered in the next brief, and there is no cap on query count. Auth requirements and the list response shape are not covered.

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 core value proposition, followed by mode guidance and the no-cap reassurance. Each sentence does work, though the no-cap note is the least essential.

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?

Covers purpose, delivery timing, modes and the destructive path for a 6-parameter, annotation-covered tool with no output schema. It is still thin on the matching semantics — how terms, negative, and min_score combine — which an agent needs to build a useful standing query rather than an empty or overly broad one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% across 6 parameters, so the description must carry the burden and it mostly does not. It explains 'remove_id' and the no-argument list mode, but 'name', 'kinds', 'terms', 'min_score' (1-100) and the interaction of 'negative' with 'terms' are left entirely to the schema.

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?

States a specific verb and resource ('register a standing query') and frames the mechanism as push-based ('future matches come to you instead of waiting to be found'), which implicitly separates it from the pull-based search/match siblings. It also discloses the two alternate modes (list, delete). It stops short of naming a sibling, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete mode-selection guidance: no arguments to list your existing queries, 'remove_id' to delete one. That resolves the otherwise confusing empty-required-parameters schema. It does not say when a standing query is a poor choice versus one-off search, but the usage context is clear.

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