Skip to main content
Glama

list_agent_tools

Read-only

Lists the flow actions, subflows, scripts, topics, skills, and MCP tools attached to an Otto AI agent, or finds which agents use a specified tool.

Instructions

List the tools attached to an Otto (Now Assist) AI agent in AI Agent Studio: flow actions, subflows, scripts, topics, skills, MCP tools, etc. Reads sn_aia_agent_tool_m2m joined to sn_aia_tool. Pass an agent sys_id or exact name, or a tool to see which agents use it.

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

Input Schema

NameRequiredDescriptionDefault
toolNoOptional: sn_aia_tool sys_id, to list the agents a tool is attached to
agentNoAgent sys_id or exact agent name (sn_aia_agent)
limitNoMax records (default 100)
activeNoFilter on link active flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.9/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 description adds useful backend context by naming the sn_aia_agent_tool_m2m join to sn_aia_tool, which hints at the shape of returned link records, but it says nothing about pagination behavior beyond the schema default, ordering, or result size.

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?

Three tight sentences with the purpose and returned tool types front-loaded, followed by the data source and the invocation options. No filler or restated boilerplate.

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?

With no output schema and no required parameters, the description should cover what a zero-argument call returns and roughly what fields come back. It gestures at this via the m2m table join but leaves the default full-listing behavior and result structure implicit.

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 each of the four parameters is already documented in structured form. The description adds marginal value by framing agent-vs-tool as mutually exclusive query modes, but it does not clarify limit semantics, active-flag meaning, or name-matching behavior beyond what the schema states.

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-plus-resource (list the tools attached to an Otto AI agent) and enumerates the concrete tool types returned (flow actions, subflows, scripts, topics, skills, MCP tools). It also describes the reverse query mode, which cleanly separates it from the attach_agent_tool / detach_agent_tool siblings.

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

Usage Guidelines4/5

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

Explicitly tells the agent which parameter selects which mode: an agent identifier lists tools, a tool identifier lists agents. That is clear invocation context, but there is no stated when-not guidance, no mention of what happens if all parameters are omitted, and no named alternative for other listing needs.

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