Skip to main content
Glama

Explore Berrys creative playbooks

playground_skills_discover
Read-onlyIdempotent

Explore built-in playbooks without opening or creating a project. Search by query/category and follow nextOffset. Include projectId only to include that project’s private skills after an access check. Skills teach a method; they do not grant permissions or spend credits. Returns matching skill summaries and pagination information.

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_skills_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return in this page.
queryNoSearch words describing the item or content to find.
offsetNoNumber of matching results to skip; use the previous response’s nextOffset for another page.
categoryNoCreative playbook category to filter discovery results.
projectIdNoProject ID for project-specific access or skills; omit for general capabilities or built-in skills.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
totalYes
skillsYes
categoriesYes
nextOffsetYes

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?

Beyond readOnlyHint/idempotent/non-destructive annotations, it discloses that projectId triggers an access check and that skills 'do not grant permissions or spend credits' — a genuine side-effect assurance the annotations can't express. Pagination behavior via nextOffset is also mentioned.

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?

Five short sentences, scoping constraint front-loaded, no filler. 'Returns matching skill summaries and pagination information' is mildly redundant given an output schema exists, but it usefully sets expectations.

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?

Rich annotations and an output schema already cover safety profile and return shape, and the description supplies the remaining essentials: project gating, access check, no credit spend, and pagination flow. It does not detail filtering behavior for query/category, a minor gap for a 5-param tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: projectId is conditionally gated and triggers an access check, and offset is meant to be fed from the prior response's nextOffset. Those are workflow semantics the schema descriptions only partially convey.

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 ('Explore built-in playbooks') and clarifies scope relative to project context ('without opening or creating a project'). It doesn't name the sibling discovery tools (playground_capabilities_discover, playground_actions_discover), so differentiation is by resource noun only, which is clear but not explicit.

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 clear conditional guidance: omit projectId for built-in skills, include it only to surface that project's private skills. It describes the discovery context well but never names an alternative tool or an explicit when-not-to-use case.

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.