Skip to main content
Glama

Retry application

retry_application
Destructive

Re-run an Application's analysis lane (create/update). Works on a failed application and also on a healthy one whose stored analysis should be refreshed (e.g. after platform detection improvements). Refuses while the application is mid-operation or already has an active job.

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": {
      "application_id": "<application_id>"
    },
    "name": "retry_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this a destructive, non-idempotent write, and the description adds valuable preconditions the annotations do not carry: it refuses when the application is mid-operation or already has an active job. It does not say what happens to the previous stored analysis when the lane is re-run, which is the main remaining behavioral gap.

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 sentences, front-loaded with the action, then the valid use cases, then the refusal conditions. Every sentence carries information the agent needs and none repeats the annotations or schema.

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 one-parameter mutation with destructive/non-idempotent annotations, the description covers the trigger conditions and the blocking preconditions, which is what an agent needs before calling it. The main omission is what the re-run overwrites in the stored analysis, which is relevant given destructiveHint=true.

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 100% for the single application_id parameter, so the schema already does the work. The description adds no further meaning about the identifier (for example, how to obtain it), which is the baseline-3 outcome for a fully documented schema.

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

Purpose5/5

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

The description names a specific verb and resource ('Re-run an Application's analysis lane (create/update)') and scopes it to analysis, distinguishing it from the retry_data_run and retry_execution siblings. An agent can tell what this tool does without opening the schema.

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?

It gives clear trigger conditions (failed application, or healthy application with stale analysis such as after platform-detection improvements) and explicit refusal conditions (mid-operation, active job). It does not name an alternative tool for the stale-analysis case, so it stops short of a 5.

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.