Skip to main content
Glama

discover_operations

Read-only

Find advanced instrument operations by task and retrieve exact schema/effects via operation ID. Results stay compact; no instrument access or execution occurs.

Instructions

Find advanced capabilities by task. Supply an operation ID to get its exact schema and effects.

No instrument access. Planned entries cannot execute; search results stay compact.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
operationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior: results can include planned entries that cannot execute, and search output is compact so an ID lookup is needed for full schema and effects. It does not explain permissions, limits, or what "task" matching looks like.

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?

Four short, front-loaded fragments with no filler; the lookup-by-ID behavior appears early. Slight terseness ("No instrument access" as an unanchored fragment) costs a little clarity but nothing is wasted.

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 an output schema exists, return-value detail is unnecessary, and annotations cover the safety profile. For a two-mode discovery tool with optional params, the description covers both modes and the planning caveat; only query semantics and result ordering are left implicit.

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, and it does assign roles: query for task-based discovery, operation for retrieving exact schema/effects. However, it omits the ID format, what an empty query returns (both default to empty/null and are optional), and whether results are ranked or truncated.

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 uses a specific verb plus resource ("Find advanced capabilities by task") and adds a second, distinct mode ("Supply an operation ID to get its exact schema and effects"). That reflective/lookup purpose sets it apart from sibling operation tools like advanced_control or measure, though "advanced capabilities" remains somewhat fuzzy as a description of what an operation actually is.

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 gives clear context for both call patterns: a task query for discovery, or an operation ID for exact schema and effects. The clause "No instrument access" implicitly excludes it from actual measurement/control work, but it never explicitly says when not to use it or redirects to a sibling tool.

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