Skip to main content
Glama

studio_context

Read-only

Fetches versioned development context for a project and state around a specified anchor, letting agents inspect related artifacts, changes, and evidence before acting.

Instructions

studio context

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": {
      "arguments": "<arguments>"
    },
    "name": "studio_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.1

TDQS

D1.1/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, but the description adds nothing beyond that: no disclosure of scope, pagination, or what the anchor/state parameters actually retrieve. For a deeply nested retrieval call the description carries no behavioral information whatsoever.

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

Conciseness2/5

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

The phrase is not padded, but brevity here is under-specification rather than conciseness. Two words for a schema with a required nested anchor object and nine sibling fields leaves the definition structurally empty.

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

Completeness1/5

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

The tool has a complex nested required-arguments schema, no output schema, and rich enum/locator options, yet the description supplies none of the context needed to invoke it correctly. Nothing compensates for the 0% schema coverage.

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

Parameters1/5

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

Schema description coverage is 0% and the input is a nested object containing anchor (with kind enum and seven optional locators), basis, intent, state_id, project_id, since_state, delta_after, after, and limit. The description explains none of these, so an agent has no basis for constructing anchor.kind or understanding basis/intent.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the tool name restated in lowercase ("studio context"), with no verb and no indication of what "context" means or what is returned. It does not distinguish this tool from context, studio_related, or the other context-oriented siblings. An agent cannot determine the tool's purpose from this text.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusions, and no mention of any alternative despite a crowded set of sibling tools (context, get_bot_context, studio_related, studio_work). Nothing tells the agent what situation selects this tool over its neighbors.

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