Skip to main content
Glama

studio_fail

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Mark your own game's active studio request failed and explain why. The owner can queue another request.

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": {
      "request": "<request>",
      "note": "<note>"
    },
    "name": "studio_fail"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
requestYesRequest id from studio_wait.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The description adds authentication requirements (OAuth or Bearer header), ownership restriction ('your own game'), and the consequence that the owner can queue another request. These are useful beyond the annotations, which already declare non-destructive and non-idempotent behavior. It does not contradict the annotations.

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 description is three sentences with no wasted wording: authentication, action, and consequence. It is front-loaded enough to use quickly, though the auth sentence leads before the purpose.

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?

For a simple two-parameter mutation with annotations covering safety and no output schema, the description provides sufficient context: auth, ownership, action, and what the owner can do next. It does not explain what happens to the failed request beyond enabling a new request, but no critical calling information 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?

Schema coverage is 50%; the request parameter is documented in the schema as the request id from studio_wait. The description's 'explain why' gives purpose to the note parameter, but does not add format or content guidance beyond the schema's length constraint.

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: 'Mark your own game's active studio request failed and explain why.' The scope (own game, active studio request) distinguishes it from change-related siblings like change_fail, though it does not explicitly name alternatives such as studio_done.

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 implied by the purpose — use when your own active studio request has failed. It adds that the owner can queue another request, but it does not state when not to use it or explicitly compare it with studio_done or change_fail.

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