Skip to main content
Glama

aw.input.commit

Verify ALL staged bytes/hash/original format and atomically publish one current immutable input. Exact completed retries recover its receipt; invalid/partial data never retires a 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": {
      "session": "<session>",
      "inputId": "<inputId>",
      "attempt": "<attempt>"
    },
    "name": "aw.input.commit"
  }
}

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

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses atomicity, immutability of the published input, idempotent retry semantics via a recovered receipt, and failure behavior ('invalid/partial data never retires a job'). It does not say whether a failed verification leaves the session usable or must be aborted, which is the remaining 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?

Two dense sentences, front-loaded with the primary action and followed by the retry and failure guarantees. No filler; every clause carries distinct operational meaning, even if the phrasing is terse and jargon-heavy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with no output schema, the description should ideally say what the returned receipt contains and what happens to the session on a validation failure. It covers the happy path, idempotency, and rejection semantics but leaves those two operational questions open.

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 only 33% — only `session` is documented, and `inputId`/`attempt` are bare UUID patterns. The retry/receipt sentence implicitly establishes `attempt` as an idempotency token, which is genuinely non-obvious, but `inputId` is left to be inferred from its name alone.

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?

States a specific verb set and resource: verify all staged bytes/hash/original format, then atomically publish one immutable input. This clearly marks it as the finalize step of the input pipeline, distinct from begin/write_chunk/abort/status siblings by implication of 'staged' data, though no sibling is named explicitly.

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 rather than spelled out: you commit after staging bytes, and identical completed retries return the receipt instead of re-publishing. There is no explicit statement of when to prefer aw.input.abort or aw.input.status, nor what to do when verification fails.

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