Skip to main content
Glama

sn_a2a_expose_agent

Enable or disable third-party A2A access for a ServiceNow AI agent, controlling whether external parties can connect to that agent.

Instructions

Turn third-party (A2A) access on or off for a ServiceNow AI agent ("Allow third party to access this AI agent"). REQUIRES WRITE_ENABLED=true and AI agent admin rights.

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

Input Schema

NameRequiredDescriptionDefault
agentYesAgent sys_id or name
exposedNotrue to allow A2A access, false to remove it (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description adds real context beyond them: a required environment flag and an admin-privilege requirement, both of which materially affect whether the call can succeed. It stops short of saying what happens to existing A2A consumers when access is revoked, which is the main remaining behavioral gap.

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?

Two sentences, zero waste: the action and resource are front-loaded, the product-equivalent label aids disambiguation, and the hard precondition is capitalized so it reads as a gate.

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 simple two-parameter toggle with no output schema, the description covers purpose, direction (on and off), and the operational prerequisites. It could say more about the effect of removal (whether existing A2A peers lose access immediately), but nothing essential to invoking it correctly is missing.

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 both parameters (agent sys_id/name, exposed boolean with its default) are already fully documented in structured form. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turn third-party (A2A) access on or off for a ServiceNow AI agent') plus the exact product UI label, so an agent can tell it apart from read-oriented siblings such as sn_a2a_get_agent_card or sn_a2a_list_agents without opening the schema.

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?

The use case (enabling/disabling A2A exposure on an agent) is clear and the required preconditions (WRITE_ENABLED=true, AI agent admin rights) are given. However, no alternative or exclusion is named — nothing tells the agent when not to use this versus agent-creation or MCP-registration siblings, so guidance stays implied.

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