Skip to main content
Glama

get_ai_asset

Read-only

Fetch a single AI Control Tower asset by sys_id to inspect governance details, lifecycle phase, risk, and linked assessment or approval requests and tasks.

Instructions

Get one AI Control Tower asset (alm_ai_digital_asset) with its governance details, lifecycle phase, risk, and any assessment / approval requests and tasks. Works for Otto (Now Assist) skills, AI agents, prompts, models and MCP assets.

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": {
      "sys_id": "<sys_id>"
    },
    "name": "get_ai_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYessys_id of the alm_ai_digital_asset (or of its sn_ai_governance_asset_governance_details record)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds real value by disclosing that the response is an aggregate: governance details, lifecycle phase, risk, and any related assessment/approval requests and tasks. It does not mention failure behavior on an unknown sys_id, which keeps it from a 5.

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 filler: identity of the record type and the returned payload come first, and the applicable asset types follow as a scoping note. Nothing redundant with the title or 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 one required parameter, no output schema, and read-only annotations, the description needs to convey the return shape, and it does by listing the included fields and the side-loaded requests/tasks. Minor gaps remain around error behavior and whether the aggregation is always included.

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% and the schema itself already explains that the sys_id may be either the asset record or its sn_ai_governance_asset_governance_details record, so the description has nothing to add. Baseline 3 applies when the schema carries parameter meaning.

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 names a specific verb and resource ('Get one AI Control Tower asset') and pins the underlying table (alm_ai_digital_asset), plus enumerates the asset categories it covers (Otto skills, AI agents, prompts, models, MCP assets). It does not distinguish itself from nearby siblings such as get_asset or get_ai_agent, so an agent still has to infer which getter applies.

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: 'Get one ... asset' signals a single-record fetch and the asset-type list hints at where it applies. There is no explicit when-to-use versus list_ai_assets (many records) or get_asset (generic asset getter), and no stated prerequisites or exclusions.

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