Skip to main content
Glama

search_operations

Read-only

Search operations across node types by app name or intent ('xero', 'send sms', 'create payment link'), the best fit first: an app the query names leads with its operations; otherwise up to three per app, the most used apps first among those that fit as well. detail_level: 'name' | 'description' (default: the opening of each one's description) | 'full' (its whole description and config schema). Scope with node_types, or search all. Progressive disclosure over the thousands of operations without loading them all. A note says when nothing is named the query.

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": "<query>"
    },
    "name": "search_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
node_typesNo
detail_levelNodescription

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description still adds real substance: ranked ordering ('the best fit first'), grouping rules (up to three per app, most used apps first), and a note emitted when nothing matches. It stops short of describing pagination or how limit interacts with result counts.

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

Conciseness3/5

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

The core information is front-loaded, but the middle is a dense semicolon chain that buries the ranking rules, and the trailing fragment 'A note says when nothing is named the query' is garbled and unclear. Trimming or restructuring that final sentence would tighten it considerably.

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?

An output schema exists, so return values need no prose, and annotations cover the safety profile; the description fills remaining gaps with ranking behavior and detail modes. The only real omission is limit semantics, which matters for a search that can return many operations.

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 0%, so the description must carry parameter meaning. It does explain detail_level's three modes and their defaults, node_types scoping, and query intent well, but the limit parameter is never mentioned despite its default of 30 — leaving one of four parameters undocumented in both places.

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 gives a specific verb and resource ('search operations across node types') plus concrete query examples ('xero', 'send sms', 'create payment link'), so an agent knows exactly what is being retrieved. It does not explicitly contrast itself with the nearby get_node_operations or search_credentials tools, which keeps it from a 5.

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?

It names the use case (find operations by app name or intent) and frames its role as 'progressive disclosure over the thousands of operations without loading them all', which tells the agent to use it as a lookup before fetching full detail. What is missing is an explicit exclusion or named alternative for when a direct node lookup is preferable.

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.