Skip to main content
Glama

Get the project the user has open

playground_context_current
Read-onlyIdempotent

Use only when the user asks to work on their open project or selection. Return lightweight context from an authorized editor active in the last 2 minutes. Never choose a recent or unrelated project. General questions about Berrys do not need this tool. Does not open or render a canvas; use playground_canvas_open only when a preview is requested or needed for the task. Returns whether editor context exists and, when available, the current project and selection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
liveNo
nextNoSuggested next action; it does not authorize spending.
sourceYes
projectYes
clientIdNo
revisionNo
canvasUrlNo
nodeCountNo
selectedNodesNo
presenceUpdatedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, yet the description still adds real context: the 2-minute activity window, the authorization requirement, and the fact that it does not open or render a canvas. It stops short of describing error/empty states beyond 'whether editor context exists'.

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?

Sentences are short and ordered from trigger to exclusions to alternatives to return value, which is well front-loaded. The final sentence partially restates what the output schema already conveys, a minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only context fetch with an output schema and rich annotations, the description covers the trigger, the staleness window, the alternative for rendering, and the shape of the result. Nothing an agent needs to call it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly adds no parameter detail and instead spends its words on scoping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Return lightweight context from an authorized editor'), scopes it to the 'open project or selection', and explicitly distinguishes itself from playground_canvas_open and from general Berrys questions. An agent can identify this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('only when the user asks to work on their open project or selection'), an explicit exclusion ('General questions about Berrys do not need this tool'), a negative constraint ('Never choose a recent or unrelated project'), and names the alternative for previews (playground_canvas_open).

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.