Skip to main content
Glama

list_ai_assets

Read-only

List AI assets from the AI Control Tower inventory—models, prompts, datasets, systems, agents, and MCP servers—with governance status, risk, and lifecycle phase; filter by name, class, or status.

Instructions

List AI assets from the AI Control Tower inventory (alm_ai_digital_asset and its model / prompt / dataset / system / MCP classes), with governance status, risk and lifecycle phase (sn_ai_governance_asset_governance_details). Covers Otto (Now Assist) skills, AI agents, prompts, models and MCP servers.

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

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name contains
limitNoMax records (default 50)
risk_scoreNoRisk value, e.g. 1 High, 2 Medium, 6 Critical
asset_classNoAsset class (default all)
install_statusNoAsset install_status value, e.g. 1 (Installed/Deployed)
lifecycle_phaseNoLifecycle phase name, e.g. New, Assess, Build, Deploy, Offboard
governance_statusNoGovernance status value: 1 In review, 2 Approved, 4 Deployed, 5 AI steward review, 8 Approved for deployment, 9 Canceled, 10 Offboarded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.5/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 genuine context beyond that by naming the underlying tables and the taxonomy it spans (Otto skills, agents, prompts, models, MCP servers), but it says nothing about ordering, pagination beyond the schema's limit, or result volume expectations for a potentially large inventory.

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?

Two sentences, front-loaded with the core scope, then the coverage detail. The parenthetical table names are dense but functional for grounding the agent; there is little waste.

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 seven-parameter, no-required-argument read tool with no output schema, the description adequately establishes the inventory scope, the class taxonomy, and the attribute domains (governance, risk, lifecycle). A brief note on result shape or ordering would close the remaining gap, but nothing essential to correct invocation 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 all seven parameters are already documented with examples and value meanings, which sets the baseline at 3. The description's mention of governance status, risk and lifecycle phase mirrors those filters but adds no syntax or semantics the schema does not already provide.

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 and resource (list AI assets from the AI Control Tower inventory) and enumerates the concrete classes covered (model, prompt, dataset, system, MCP) plus the governance-details source. It does not, however, explicitly distinguish itself from nearby siblings like list_ai_agents or list_assets, even though it overlaps with them by naming AI agents as a covered class.

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 implied by the scope statement: this is the inventory-wide listing that spans all asset classes. There is no explicit when-to-use versus when-not guidance, and no direction to a narrower sibling such as list_ai_agents when only agents are wanted, so the agent must infer the routing.

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