Skip to main content
Glama

execution_status

Retrieve the status and metadata of an execution by ID, or default to the running or most recently accepted one to check progress and outcomes.

Instructions

返回一个 execution 的状态与元数据。

选择规则

提供 execution 时,只选择该正整数记录。省略时,先选择当前 running 记录;不存在 running 记录时,选择最近一次被接受的记录; 两者都不存在时返回 execution_not_found。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "execution_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
executionNo要查看的正整数执行编号。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / execution / description
      Previous value: -"要查看的正整数执行编号。省略时使用当前记录,随后\n使用最近记录。"New value: +"要查看的正整数执行编号。"
  2. Addedv0.1.13

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses fallback selection behavior and the `execution_not_found` outcome, but it does not state whether the tool is strictly read-only, what permissions are required, or what the returned status/metadata structure looks like.

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?

The description is front-loaded with the tool purpose and then presents compact selection rules. Every sentence contributes useful information, with no redundant or filler text.

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 one-parameter read-status tool, the selection and error behavior are reasonably covered. However, with no output schema and no annotations, the description leaves the return shape and behavioral constraints underspecified, and it does not address sibling-tool differentiation.

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 already 100%, so the schema documents the integer parameter. The description adds meaningful semantics beyond the schema by explaining that providing `execution` selects only that record and omitting it triggers running/recent-accepted fallback behavior.

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 states a specific verb and resource: returning an execution's status and metadata. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling tool `status` or explain when to use this instead of that one.

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?

The selection rules explain how the optional `execution` parameter affects which record is returned, including the running/recent-accepted fallback. However, this is primarily parameter selection behavior, not guidance on when to use this tool versus sibling tools such as `status` or `read_output`.

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