Skip to main content
Glama

list_ai_agents

Read-only

Retrieve AI agent definitions and their active status from ServiceNow, with optional active filtering and record limits for inventory and auditing.

Instructions

List AI agent definitions (AI Agent Studio, sn_aia_agent) with their active flag from sn_aia_agent_config

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (default 25)
activeNoFilter by active status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.9.0

TDQS

B3.2/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 the safety profile is covered structurally. The description adds useful context by naming the source tables and noting the active flag comes from sn_aia_agent_config, but it says nothing about pagination, ordering, or what happens when limit is exceeded.

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 no filler; the resource and its source tables come first. The parenthetical table identifiers are dense but earn their place by disambiguating the underlying data source.

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 simple read-only two-parameter list tool with annotations and no output schema, the definition is mostly sufficient. It still leaves the return shape only partially implied ("definitions with their active flag") and omits any statement about result volume or paging behavior.

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 both parameters (limit with its default of 25, and the active boolean filter) are already fully documented in the schema. The description's mention of the active flag loosely corroborates the active parameter but adds no syntax or behavioral detail beyond the schema.

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?

States a specific verb and resource ("List AI agent definitions") and anchors it to concrete ServiceNow tables (sn_aia_agent, sn_aia_agent_config), which lets an agent identify the domain. It does not, however, distinguish itself from siblings such as list_external_agents or sn_a2a_list_agents, so an agent must still infer which agent-listing tool applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. The description never says whether to call this instead of get_ai_agent for a single record, or instead of list_external_agents / sn_a2a_list_agents for other agent types.

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