Skip to main content
Glama

studio_plan

Plan idempotent per-shot production assignments across separately authorized accounts within an operator-entered budget; creates no paid generations.

Instructions

Plan idempotent per-shot assignments across separately authorized accounts, within operator-entered budget; creates no paid generations.

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": {
      "projectId": "<projectId>"
    },
    "name": "studio_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNo
providerNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two valuable traits — idempotency and that no paid generations are created — but omits whether a plan is persisted, what happens to a prior plan, what authorization is required across the "separately authorized accounts," and what the call returns. It also references an "operator-entered budget" that has no matching parameter, leaving the enforcement mechanism unexplained.

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?

A single front-loaded sentence with no filler; the safety constraint is placed at the end as a qualifier where it reads naturally. The density is high but every clause carries content, so nothing needs cutting.

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

Completeness2/5

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

For a planning tool with no annotations, no output schema, and zero parameter documentation, the description leaves major gaps: what a returned plan looks like, how the budget is supplied if not as a parameter, and how account authorization is expressed. The mismatch between the promised budget input and the actual schema is a real completeness defect.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters (projectId, provider, variant), and the description never mentions any of them or explains the provider enum values. The words "per-shot" and "accounts" gesture at scope but add no concrete meaning for variant, provider, or projectId. Worse, the only concrete input it names — budget — does not exist in the schema, so it cannot guide the agent on what to actually pass.

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 ("Plan") and a specific resource ("per-shot assignments across separately authorized accounts") and draws a clear scope boundary with "creates no paid generations." This distinguishes it from execution-oriented siblings like studio_dispatch_job, though the jargon ("per-shot," "separately authorized accounts") is dense enough that a new agent may need a beat to parse it.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "creates no paid generations" signals this is the safe, pre-execution step, which contextualizes it against generative siblings. There is no explicit when-to-use statement and no named alternative (e.g. studio_preflight vs studio_dispatch_job), so the agent must infer the workflow position.

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