Skip to main content
Glama

Discover what you can make with Berrys

playground_capabilities_discover
Read-onlyIdempotent

Discover what you can make with Berrys without selecting or reading a project. Omit projectId for a general overview. For a chosen project, include projectId to check permissions before editing. Internal flags are for tool routing; explain only task-relevant limits to the user. Returns a general capability overview, or project-specific permissions, available tools and usage conventions.

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

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject ID for project-specific access or skills; omit for general capabilities or built-in skills.

Output Schema

NameRequiredDescriptionDefault
nextNoSuggested next action; it does not authorize spending.
scopeNo
toolsNo
approvalNo
guidanceNo
overviewNo
nodeTypesNo
projectIdNo
conventionsNo
capabilitiesNo
startingPointsNo
projectEditAccessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that the call surfaces permissions, available tools and usage conventions, which is useful context. The line about 'internal flags ... for tool routing' is vague and refers to nothing visible in the schema, weakening rather than clarifying behavior.

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?

The conditional scoping ('omit projectId... include projectId') is front-loaded and easy to act on, and the return summary is compact. One sentence about 'internal flags' is cryptic filler that does not map to any visible field and costs the description a point.

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?

This is a simple read-only tool with one optional parameter and an output schema, so return values need not be spelled out. The description covers both modes and the permission-checking use case. The undefined 'internal flags' reference is the only loose end.

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% and the single parameter is already documented, so the baseline is 3. The description earns a bump by explaining what including projectId is for operationally ('check permissions before editing'), which the schema does not say.

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 states a specific verb and resource ('Discover what you can make with Berrys') and explicitly scopes it as not requiring a project selection or read ('without selecting or reading a project'). It is clear what capability it exposes, though it never names its nearest siblings (playground_actions_discover / playground_skills_discover) to sharpen the boundary.

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 explicit conditional usage: omit projectId for a general overview, include projectId to check permissions before editing. That is a clear when-to-use rule tied to a concrete workflow. It stops short of naming alternative discovery tools or a 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.