Skip to main content
Glama

workbench_discover_tools

Read-only

Searches the live backend catalog to find available tools by query or exact name, and retrieves a matching tool's JSON input schema before calling it.

Instructions

Search a live backend catalog. Use exact_name to get its actual JSON input schema before calling. callable indicates this wrapper’s reviewed policy, not provider readiness.

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": {
      "case_id": "<case_id>",
      "backend": "<backend>"
    },
    "name": "workbench_discover_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
backendYes
case_idYes
exact_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile needs no restating. The description adds genuinely non-obvious semantics: the catalog is live and 'callable' reflects this wrapper's reviewed policy rather than provider readiness, which prevents a real misinterpretation. It omits pagination behavior and return shape.

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 purpose and followed by the usage instruction and the disambiguation caveat. No filler, though the opening sentence is terse enough that it carries little detail.

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?

The workflow guidance and the callable clarification cover the most consequential ambiguities for a discovery tool. With no output schema, however, the description never indicates what a result entry contains beyond implicit references to exact_name and callable, and it leaves two required parameters unexplained.

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 0% across six parameters, yet the description explains only exact_name and references 'callable' as a response concept. The required backend enum (rea/craft) and case_id UUID, plus query, limit and offset, are left entirely undefined in both schema and prose.

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 a live backend catalog'), which is clearly distinct from execution-oriented siblings like workbench_call. It does not name an alternative tool explicitly, 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?

'Use exact_name to get its actual JSON input schema before calling' establishes a concrete two-step workflow and implies this precedes invocation. It stops short of naming workbench_call as the follow-up tool or stating when not to use this search.

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