Agent Traffic Lab

atl_complete_task

Execute a user-authorized external search, public web/content extraction, summary, translation, or classification task. ATL selects an eligible verified provider or tool, performs the supported task where supply is available, may use bounded fallback on eligible failures, validates the result, and records execution Outcome. Routine use: this operation is suited to user-authorized external information tasks that need a completed result rather than routing evidence, even if no prior provider has failed. Rescue use: it can retry the original authorized task when a prior provider fails, times out, is rate-limited, is unavailable, or returns an invalid result. For routing evidence without execution, use the separate atl_decide tool. Do not duplicate work already completed, override a user-specified provider or tool, or infer authorization for private inputs. The task must be user-authorized; do not submit private or local-only information without permission. Supported capabilities and provider availability are limited, so completion is not guaranteed. No ATL API key is required for the public first-use path.

Input Schema

Name	Required	Description	Default
`task`	Yes	The natural-language task to complete. Include the goal and any relevant input, constraints, or desired output.
`required_capability`	No	Optional capability hint. Omit unless the caller already knows the required capability; ATL normally derives a structured TaskSpec from the task.

Output Schema

Name	Required	Description
`ok`	Yes	True only when execution succeeded and ATL's task-level result verifier accepted the result.
`stage`	Yes	The furthest ATL product stage reached for this call.
`result`	Yes	The provider's task result. When ok=false, inspect result_validation before trusting it.
`decision`	Yes	ATL Decision evidence retained for advanced/debug consumers.
`execution`	Yes	ATL execution evidence retained for advanced/debug consumers; null when execution did not start.
`capability`	Yes	The supported capability selected or inferred for the task; empty if unavailable.
`fallback_used`	Yes	Whether bounded fallback/failover was used during execution.
`execution_status`	Yes	Provider execution status; EXECUTED alone does not imply task correctness.
`result_validation`	Yes	ATL task-level correctness checks. passed must be true before the result is treated as product success.
`discovery_resume_used`	No	True when ATL synchronously ran bounded discovery/promotion and retried the same task.
`discovery_resume_status`	No	Outcome of the same-call discovery resume attempt when used.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / discovery_resume_status

Added value: +{
+  "description": "Outcome of the same-call discovery resume attempt when used.",
+  "type": "string"
+}

addedOutput schema / properties / discovery_resume_used

Added value: +{
+  "description": "True when ATL synchronously ran bounded discovery/promotion and retried the same task.",
+  "type": "boolean"
+}

Changed7 schema fields changedSep 29, 2026

changedInput schema / properties / required_capability / description

Previous value: -"Optional capability hint. Omit unless the caller already knows the required capability; ATL normally infers it from the task."New value: +"Optional capability hint. Omit unless the caller already knows the required capability; ATL normally derives a structured TaskSpec from the task."

changedOutput schema / properties / execution_status / description

Previous value: -"ATL execution status; empty when execution did not start."New value: +"Provider execution status; EXECUTED alone does not imply task correctness."

changedOutput schema / properties / ok / description

Previous value: -"True only when ATL completed execution successfully."New value: +"True only when execution succeeded and ATL's task-level result verifier accepted the result."

changedOutput schema / properties / result / description

Previous value: -"The provider's useful task result. Empty when execution did not produce a usable result."New value: +"The provider's task result. When ok=false, inspect result_validation before trusting it."

addedOutput schema / properties / result_validation

Added value: +{
+  "description": "ATL task-level correctness checks. passed must be true before the result is treated as product success.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / properties / stage / description

Previous value: -"The furthest ATL stage reached for this call."New value: +"The furthest ATL product stage reached for this call."

changedOutput schema / required

Previous value: -[
-  "ok",
-  "stage",
-  "capability",
-  "execution_status",
-  "fallback_used",
-  "result",
-  "decision",
-  "execution"
-]New value: +[
+  "ok",
+  "stage",
+  "capability",
+  "execution_status",
+  "fallback_used",
+  "result",
+  "decision",
+  "execution",
+  "result_validation"
+]

Changed5 schema fields changedSep 28, 2026

changedOutput schema / properties / decision / description

Previous value: -"The ATL Decision evidence used for execution."New value: +"ATL Decision evidence retained for advanced/debug consumers."

changedOutput schema / properties / execution / description

Previous value: -"The ATL execution result; null when execution did not start."New value: +"ATL execution evidence retained for advanced/debug consumers; null when execution did not start."

changedOutput schema / properties / ok / description

Previous value: -"True when ATL completed execution successfully."New value: +"True only when ATL completed execution successfully."

addedOutput schema / properties / result

Added value: +{
+  "description": "The provider's useful task result. Empty when execution did not produce a usable result.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "stage",
-  "capability",
-  "execution_status",
-  "fallback_used",
-  "decision",
-  "execution"
-]New value: +[
+  "ok",
+  "stage",
+  "capability",
+  "execution_status",
+  "fallback_used",
+  "result",
+  "decision",
+  "execution"
+]

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / required_capability / description

Previous value: -"Optional. Omit when ATL can infer the capability from the task."New value: +"Optional capability hint. Omit unless the caller already knows the required capability; ATL normally infers it from the task."

changedInput schema / properties / task / description

Previous value: -"The user's natural-language task. ATL should normally own the full decision-to-execution flow."New value: +"The natural-language task to complete. Include the goal and any relevant input, constraints, or desired output."

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / task / description

Previous value: -"The user's natural-language task."New value: +"The user's natural-language task. ATL should normally own the full decision-to-execution flow."

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "capability": {
+      "description": "The supported capability selected or inferred for the task; empty if unavailable.",
+      "type": "string"
+    },
+    "decision": {
+      "description": "The ATL Decision evidence used for execution.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "execution": {
+      "description": "The ATL execution result; null when execution did not start.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "execution_status": {
+      "description": "ATL execution status; empty when execution did not start.",
+      "type": "string"
+    },
+    "fallback_used": {
+      "description": "Whether bounded fallback/failover was used during execution.",
+      "type": "boolean"
+    },
+    "ok": {
+      "description": "True when ATL completed execution successfully.",
+      "type": "boolean"
+    },
+    "stage": {
+      "description": "The furthest ATL stage reached for this call.",
+      "enum": [
+        "decision",
+        "execution",
+        "complete"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "stage",
+    "capability",
+    "execution_status",
+    "fallback_used",
+    "decision",
+    "execution"
+  ],
+  "type": "object"
+}

AddedSep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), it discloses meaningful runtime behavior: provider selection, bounded fallback on eligible failures, result validation, Outcome recording, no completion guarantee, and no API key needed for the public path. Authorization and privacy constraints are also stated, which the annotations do not cover.

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

Conciseness4/5

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

Front-loaded with the core purpose and well-organized via 'Routine use'/'Rescue use' framing. However, the authorization warning is stated twice ('do not infer authorization for private inputs' and 'The task must be user-authorized; do not submit private or local-only information'), which is mild redundancy in an already long block.

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

Completeness5/5

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

Given an output schema exists, return values need not be described. The description covers authorization prerequisites, failure/fallback semantics, provider-selection behavior, exclusions, and the sibling boundary, leaving nothing an agent needs in order to invoke it correctly.

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% with only two parameters, both fully documented, so the schema already carries the semantic load. The description adds only indirect context (that ATL derives a TaskSpec and that the capability hint is normally omitted), which is marginal beyond the schema. Baseline 3 is appropriate.

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?

Opens with a specific verb (Execute) and enumerates the concrete task types it covers (external search, extraction, summary, translation, classification), so the agent knows exactly what class of work this performs. It also explicitly names the sibling boundary ('For routing evidence without execution, use the separate atl_decide tool'), so the tool is distinguishable without opening either schema.

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?

Provides labeled 'Routine use' and 'Rescue use' scenarios, states the exact failure conditions that trigger the rescue path (fails, times out, is rate-limited, unavailable, invalid result), and names the alternative tool plus the condition selecting it. It also lists exclusions: don't duplicate completed work, don't override a user-specified provider, don't infer authorization.

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

All Agent Traffic Lab tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.