Skip to main content
Glama

validate_private_scenario

Read-onlyIdempotent

Check an existing scenario for validation issues without changing it (useful for repairing legacy content). A coding scenario's starter code also runs on every runtime version the editor offers, which counts toward the write rate limit. Requires private_scenarios:read.

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": {
      "scenarioId": "<scenarioId>"
    },
    "name": "validate_private_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioIdYesCanonical UUID of your owned scenario, returned by create_private_scenario or list_private_scenarios. Do not invent an ID or substitute a practice-reference ID. Ownership comes from the token, not a userId argument.

Output Schema

NameRequiredDescriptionDefault
validYes
issuesYes

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?

Adds real context beyond the annotations: the required private_scenarios:read scope and the non-obvious fact that a coding scenario's starter code runs on every runtime version, consuming write rate limit. The annotations already cover readOnly/idempotent/non-destructive, so the remaining gap is minor; the return shape is covered by the output schema.

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?

Purpose is front-loaded in the first clause, followed by a brief use case, a quota caveat, and the auth requirement. All four pieces are informative, though the quota sentence is dense and slightly interrupts the flow of the core action.

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 single-parameter, non-destructive validation tool with full annotations, a 100%-documented parameter, and an output schema, the description covers action, use case, permissions, and a hidden quota side effect. Nothing an agent needs before calling it is missing.

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

Parameters3/5

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

The single scenarioId parameter has 100% schema description coverage, including ownership and 'do not invent an ID' guidance, so the schema carries the semantics. The description adds nothing about the parameter itself, which is the expected baseline here.

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?

Opens with a specific verb and resource plus a non-mutation qualifier: 'Check an existing scenario for validation issues without changing it.' That separates it from the read-only getters in the sibling list, though it does not name get_private_scenario or the authoring guide explicitly.

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 a concrete use case ('useful for repairing legacy content') that tells the agent when this tool is worth reaching for. It stops short of explicit exclusions or naming an alternative to run first, so the routing guidance is contextual rather than definitive.

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.

Resources