Skip to main content
Glama

sn_a2a_get_agent_card

Read-only

Fetch a ServiceNow AI agent's A2A card to inspect skills, capabilities, and supported protocol versions using an agent sys_id or name.

Instructions

Fetch the A2A agent card of a ServiceNow AI agent (skills, capabilities, supported protocol versions).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent": "<agent>"
    },
    "name": "sn_a2a_get_agent_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent sys_id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.4/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. The parenthetical adds useful value beyond them by telling the agent what the response contains, but it says nothing about failure modes (unknown agent name, agent not exposed via A2A) or whether auth/exposure prerequisites apply.

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?

One sentence, front-loaded with verb and resource, with the parenthetical doing real work by listing the returned fields. There is no filler and nothing to trim.

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?

This is a simple single-parameter read tool with full schema coverage and read-only annotations, and the description contributes the response shape that no output schema provides. Only error and prerequisite behavior are left unstated, which is a minor gap at this complexity.

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 parameter is fully documented as "Agent sys_id or name." The description only restates that the target is a ServiceNow AI agent, adding no format, resolution-order, or ambiguity guidance 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?

The description gives a specific verb ("Fetch") and a specific resource ("A2A agent card of a ServiceNow AI agent"), then parenthetically enumerates the card's contents (skills, capabilities, supported protocol versions). This clearly separates it from the broader agent tools in the sibling list, though it never names a sibling it replaces.

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 explicit when-to-use or when-not-to-use guidance and no mention of an alternative such as sn_a2a_list_agents or get_ai_agent. The only implied usage comes from the term "A2A agent card" itself, so the agent must infer that this is a discovery step.

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