Skip to main content
Glama

get_otto_status

Read-only

Reports installed and enabled AI capabilities on a ServiceNow instance, including Otto/Now Assist, AI Agents, MCP, Knowledge Graph, versions, key properties, and agent/tool/trigger/deployment counts.

Instructions

One report of what AI is available on this instance: installed Otto / Now Assist, Generative AI Controller, AI Agents, MCP server/client, Knowledge Graph and AI Control Tower apps with versions (sys_scope), key properties (sn_aia.external_agents.enabled, sn_aia.enable_mcp_tool) and counts of agents, tools, triggers and deployments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds what an agent cannot get elsewhere – that the report returns app versions via sys_scope, specific properties (sn_aia.external_agents.enabled, sn_aia.enable_mcp_tool) and counts of agents, tools, triggers and deployments. It stops short of stating performance cost or whether disabled/unlicensed components appear.

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 front-loaded sentence leading with the deliverable, then a compact list of contents. The parenthetical property names and component list are dense but each item conveys concrete payload detail that is unavailable elsewhere since there is no output schema.

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 zero parameters, no output schema and only read-only annotations, the description carries the burden of describing return contents and does so thoroughly. Minor gaps remain: no mention of permissions needed or whether the report aggregates across workspaces.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumeration of returned fields is a bonus rather than a parameter explanation.

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-plus-resource: one report of what AI is available on this instance, then enumerates the components covered (Otto/Now Assist, Generative AI Controller, AI Agents, MCP, Knowledge Graph, AI Control Tower). An agent can tell it is an aggregate inventory read, though it does not explicitly differentiate itself from siblings like sn_mcp_status or get_current_instance.

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 through 'what AI is available on this instance' – an agent can infer it is the discovery/overview call before drilling into specific tools. There is no explicit when-to-use, when-not-to-use, or named alternative such as sn_mcp_status for MCP-only checks.

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