Skip to main content
Glama

list_external_agents

Read-only

Lists external third-party AI agents and their providers, protocols, discovery configs, agent cards, skills, connection settings, and external agent records for Otto/Now Assist A2A use.

Instructions

List external (third-party) AI agents registered for Otto / Now Assist A2A (Agent2Agent) use: providers (sn_aia_external_agent_provider), protocols, discovery configs, agent cards and skills, connection configurations, and sn_aia_agent records of type external.

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_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per section (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered structurally. The description adds genuine value by disclosing that results span multiple record categories (sections), which explains the 'limit per section' semantics, but it says nothing about pagination beyond that, ordering, or what happens when a section is empty.

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?

A single front-loaded sentence with the purpose first and the enumerated contents after the colon. Dense but every clause carries information; minor cost is the long enumeration that reads like a schema dump.

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 usefully compensates by listing the kinds of records that come back across sections. For a read-only, zero-required-parameter listing tool the remaining gap is routing guidance against similarly named siblings, not correctness of invocation.

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% and the single `limit` parameter is fully documented in the schema as 'Max rows per section'. The description does not restate or extend parameter meaning beyond implying multi-section results. With one well-documented, optional parameter, the baseline 3 applies.

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 verb and resource ('List external (third-party) AI agents'), qualifies the scope with the A2A/Now Assist domain, and enumerates what is included (providers, protocols, discovery configs, agent cards, skills, connection configs, external sn_aia_agent records). It implicitly separates external agents from the plain `list_ai_agents` sibling via 'third-party', but never names or contrasts an alternative 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 only implied by the scope qualifier 'external (third-party) ... for A2A use'. There is no explicit statement of when to pick this over `list_ai_agents` or `sn_a2a_list_agents`, nor any exclusion or prerequisite guidance.

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