Skip to main content
Glama

studio_record_failure

Records confirmed upstream failures and marks unknown submissions as blocked pending operator CLI reconciliation.

Instructions

Record a confirmed upstream failure. Unknown submissions remain blocked until operator CLI reconciles them.

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": {
      "jobId": "<jobId>",
      "status": "<status>"
    },
    "name": "studio_record_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
jobIdYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a genuine side effect: unknown submissions remain blocked pending operator CLI reconciliation. It omits other behavioral facts an agent needs for a mutation tool — idempotency on repeat calls, permission requirements, and what is returned on success.

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?

Two short sentences with the action front-loaded and a consequential caveat second — no wasted wording. It is arguably too terse for a mutation tool rather than bloated, which is why structure scores well but completeness does not.

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?

A destructive-by-nature recording tool with no annotations, no output schema, and 0% parameter documentation demands more than two sentences. The blocking/reconciliation behavior is captured, but the parameter contract and the call/response consequences are left undocumented.

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, so the description must compensate and does not. It never explains jobId (a strict UUID), the status enum values ("failed" vs "submission_unknown"), or the purpose and limits of the optional note field, leaving an agent to infer the enum semantics from one oblique sentence.

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

Purpose3/5

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

The verb+resource is present ("Record a confirmed upstream failure"), but the scope is muddled by the second sentence about unknown submissions, and the sibling tools (studio_ingest_result, studio_status, studio_dispatch_job) are never referenced. An agent can guess the general intent but cannot cleanly separate this from other studio_* result-reporting tools.

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?

"Confirmed upstream failure" implies a precondition for use, and the note that unknown submissions stay blocked hints at the boundary case. However, there is no explicit statement of when to call this versus studio_ingest_result or when to leave the job alone, so the guidance is inferred rather than stated.

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