Skip to main content
Glama

list_external_agent_runs

Read-only

Lists inbound and outbound external agent runs with protocol, method, state, related record, and direction/state totals; optionally includes payload snippets. Read-only.

Instructions

A2A and external agent traffic (sn_aia_external_agent_exec_history): inbound and outbound messages and tasks with protocol, method, state and the record they relate to, plus totals by direction and state. Payloads are left out unless include_payload is true. Read-only.

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": "list_external_agent_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook back this many days (default 30)
limitNoMax runs (default 25)
directionNoOnly one direction
include_payloadNoInclude the first 500 characters of each payload (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description correctly reinforces read-only rather than contradicting it. Beyond the annotations it adds genuinely useful behavior: the result includes aggregates by direction and state, and payloads are omitted by default with only a first-500-character excerpt when requested. That payload-suppression detail is the kind of cost/privacy behavior an agent cannot get from the annotations alone.

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?

Two compact sentences, front-loaded with the resource and its table, then the payload caveat, then the read-only flag. Nothing is padded, though the parenthetical table name is a minor density cost for an agent that only needs the semantics.

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?

With no output schema, the description does the work of describing the return shape (messages and tasks with protocol, method, state, related record, plus direction/state totals), which is exactly what is needed. All four optional parameters are schema-documented. The only missing piece is any hint of pagination or volume behavior given the limit parameter.

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 100%, so days, limit, direction and include_payload are already documented in the input schema. The description only echoes the include_payload default behavior and says nothing extra about the lookback window, limit semantics, or the direction enum. Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific resource ('A2A and external agent traffic', with the backing table sn_aia_external_agent_exec_history) and enumerates what the records contain (protocol, method, state, related record, direction/state totals). That is well beyond a restatement of the name. It stops short of distinguishing itself from close siblings such as list_external_agents or list_ai_agent_executions, so it lands at 4 rather than 5.

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 by the scope statement: an agent can infer this is the tool for inspecting inbound/outbound A2A message and task history. However, there is no explicit when-to-use guidance, no exclusion of related siblings, and no statement of prerequisites. Adequate but with a clear gap.

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

Deploy Server

Other Tools