Skip to main content
Glama

Find saved Berrys workflows

playground_workflow_search
Read-onlyIdempotent

Find accessible saved project workflows by name. Returns workflow IDs for inspection and staged execution. This does not search public templates.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSearch words describing the item or content to find.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
truncatedYes
workflowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description still adds useful behavior beyond them: results are limited to accessible saved project workflows and return IDs rather than full definitions, and public templates are out of scope.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and scope, followed by the return value and the exclusion. Every sentence carries distinct information with no repetition of the title or annotations.

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 not be described in depth, and the safety profile is fully annotated. The main residual gap is the behavior of the optional query defaulting to an empty string (return-all vs. error) and any result-count limits, which an agent would want before calling.

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 coverage is 100% and the single optional 'query' parameter is fully documented in the schema. The description's phrase 'by name' adds a slight hint about matching semantics but does not clarify what an empty (default) query returns, so it stays at the baseline.

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 names a specific verb and resource ('Find accessible saved project workflows by name') and scopes it to saved, accessible project workflows, explicitly excluding public templates. It stops short of naming a sibling tool (e.g., playground_workflow_inspect) as the next step, so it is clear but not maximally differentiated.

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 establishes the entry point in a workflow: find by name, then use the returned IDs for inspection and staged execution, which is real when-to-use guidance. It also states a clear exclusion ('does not search public templates'), though it gives no guidance for the case of an empty or broad query.

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.