Skip to main content
Glama

ai_modeling_retry

Request a free project-generation retry only when Studio reports can_retry=true, using a stable request_id to reuse the original job and prevent duplicate or unsafe retries.

Instructions

request a free project generation retry only when Studio reports retry_info.can_retry=true. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_retry"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

The annotations say the tool is a non-read-only, non-destructive, open-world operation. The description adds idempotency semantics: reusing a request_id returns the original job, changed input conflicts, and outcome_unknown is unsafe to retry. It does not say what happens when max_estimated_credits is exceeded or what the retry job returns, so it misses some behavioral detail.

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

Conciseness5/5

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

Three short sentences, each carrying a distinct constraint: the precondition, the account and idempotency model, and the conflict and outcome_unknown rules. The gating condition comes first, and there is no filler.

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 mutating retry call with no output schema, it covers the critical safety rules (when retry is legal, idempotency, outcome_unknown) and shows how the call is authenticated via the Studio account. It is nearly complete, with the only real gap being the credit-cap semantics.

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 description coverage is 0% across three required parameters, so the description must carry the semantics. It explains request_id well as a stable idempotency key, including conflict on changed input, and hints that the parameters object determines identity. However, it never explains max_estimated_credits, the credit cap, or project_id.

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 gives a specific verb and resource: 'request a free project generation retry'. It also scopes the action with the precondition that Studio's retry_info.can_retry must be true. It does not name a sibling tool, but the purpose is clear enough for an agent to distinguish a retry from the original generation call.

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

Usage Guidelines5/5

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

This definition gives both the positive trigger and the exclusion: call only when retry_info.can_retry=true, and never blindly retry an outcome_unknown state. That is explicit when-to-use and when-not-to-use guidance, not inference.

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

Deploy Server

Other Tools