Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___get_tasks

Poll status of long-running tasks. Use after a tool call returns task_id with status "working". Up to 3 IDs per call. Tasks expire after 5 min. Pass poll_iteration (start at 1, increment each call) and follow the recommended_wait_seconds in the response before polling again.

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": {
      "task_ids": "<task_ids>"
    },
    "name": "aws-mcp__aws___get_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idsYesOne or more task IDs (up to 3) from previous tool invocations.
poll_iterationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 does well: it discloses the 3-ID batch limit, the 5-minute task expiry, the polling cadence recommendation, and the existence of a recommended_wait_seconds field in the response. Remaining gaps are error behavior for expired or unknown task IDs and whether completed-task results are returned inline, but the key lifecycle constraints are covered.

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?

Four short sentences, each independently load-bearing: purpose, trigger condition, batch limit, expiry, and polling protocol. The trigger condition is front-loaded immediately after the purpose, and there is no filler or restatement.

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 two-parameter polling tool with no output schema, the description supplies the trigger, the batch limit, the expiry window, and how to interpret the response's wait-time field — enough for correct invocation. It stops short of describing what a terminal (completed/failed) task returns, which is the main remaining question an agent would have.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, and the description compensates well for the weaker parameter: it explains that poll_iteration starts at 1, increments on each call, and exists to drive suggested wait times — semantics beyond the schema's bare 'poll attempt number.' task_ids gains the context that IDs come from prior tool invocations and are capped at 3, reinforcing the schema's note.

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 opens with a specific verb and resource: 'Poll status of long-running tasks,' naming both the async pattern and the precondition (a prior tool call returned task_id with status 'working'). It does not name a sibling tool explicitly, but the async-polling purpose is unambiguous against synchronous getters like get_job or get_readiness_result.

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 states exactly when to invoke this tool — after a tool call returns a task_id with status 'working' — and adds operational cadence (follow recommended_wait_seconds before polling again). It does not spell out when not to use it or what to do when a task has already completed, but the trigger condition is concrete enough that an agent can act on it.

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.