Skip to main content
Glama

sn_a2a_list_agents

Read-only

List ServiceNow AI agents and see which are exposed to external callers over A2A, including each agent card URL. Filter by name, limit results, or show only third-party accessible agents.

Instructions

List ServiceNow AI agents (Otto / AI Agent Studio) and whether each is exposed to external callers over A2A, with its agent card URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax agents (default 25)
searchNoFilter by name
exposed_onlyNoOnly agents open to third-party (A2A) access

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds value by disclosing what comes back (per-agent A2A exposure flag and agent card URL), which matters because there is no output schema. It does not mention result ordering, pagination behavior, or what happens when no agents are exposed, but the core return shape is conveyed.

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?

A single sentence with the resource and the distinguishing output front-loaded and no filler. The parenthetical product names (Otto / AI Agent Studio) earn their place by disambiguating the data source.

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 zero-required-parameter read tool with full schema coverage and no output schema, the description covers purpose, filterable dimensions, and the key returned fields. Minor gaps remain around result volume/ordering and how an exposed agent is identified, which an agent would only learn by calling it.

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%, so all three parameters (limit, search, exposed_only) are already documented in the schema, and baseline is 3. The description restates the A2A exposure concept that backs exposed_only but adds no syntax, matching rules, or default behavior beyond what the schema supplies.

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 (List) and resource (ServiceNow AI agents from Otto / AI Agent Studio) and states the distinctive payload: A2A exposure status plus each agent's card URL. That payload framing differentiates it functionally from a plain agent lister. It does not, however, name the obvious sibling alternatives (list_ai_agents, list_external_agents, sn_a2a_get_agent_card), so an agent must infer the distinction.

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 content ('whether each is exposed to external callers over A2A'), which signals the audit/discovery case, and the schema's exposed_only flag reinforces that. There is no explicit when-to-use or when-not, and no routing to sn_a2a_get_agent_card for a single agent's card or to list_ai_agents for a non-A2A inventory.

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