Skip to main content
Glama

aw.input.status

Read-only

Resume this exact transfer attempt without returning any selected bytes. Retired/complete state is explicit.

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": {
      "session": "<session>",
      "inputId": "<inputId>",
      "attempt": "<attempt>"
    },
    "name": "aw.input.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
attemptYes
inputIdYes
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds two useful behavioral facts: no selected bytes are returned, and retired/complete state is reported explicitly rather than errors. It does not clarify whether 'resume' mutates attempt state, which is the main ambiguity an agent would have.

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

Conciseness3/5

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

Two short sentences with minimal waste, but the lead sentence is front-loaded with the confusing 'resume' framing rather than the actual purpose. Brevity here comes at the cost of clarity rather than from it.

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?

With three required parameters, no output schema and low schema coverage, the description should explain what state is returned and how the attempt identifier selects it. Instead it only asserts that retired/complete state is explicit, leaving the return shape and the meaning of attempt/inputId unaddressed.

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 coverage is only 33%, and only the session parameter carries a description (private capability, do not log). The description says nothing about inputId or attempt, whose UUID patterns and roles are left entirely to inference. It does not compensate for the coverage gap.

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 is 'Resume' applied to 'this exact transfer attempt', but the tool is named status and the description never says it reports state. 'Resume' reads like a continuation action rather than a query, so the agent must infer purpose from the name. It does not distinguish itself from siblings like aw.status or aw.input.begin.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative; the agent is not told whether to call this before aw.input.begin, aw.input.commit, or instead of aw.status. The only conditional hint is that retired/complete state is surfaced explicitly, which is not a usage rule.

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