Skip to main content
Glama

ai_modeling_assets_list

Read-only

List Studio model or image assets with bounded pagination so agents can browse assets by kind, limit, and offset.

Instructions

List your Studio model or image assets using bounded pagination.

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

Input Schema

NameRequiredDescriptionDefault
kindNomodel
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's only added behavioral detail is "bounded pagination," which hints at constrained paging but does not explain default page size, max bounds, ordering, or what an empty page means.

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?

A single front-loaded sentence with no wasted wording. It is efficient, though the brevity contributes to the gaps in usage and parameter detail rather than being a virtue in itself.

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?

Placeholder.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely does not. "Model or image" gestures at kind and "bounded pagination" gestures at limit/offset, but nothing is said about the 1–100 limit range, default 20, offset semantics, or max offset.

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 ("List") and resource ("Studio model or image assets"), and the "model or image" phrasing maps to the kind enum, so the agent knows what it returns. It does not distinguish this from the sibling ai_modeling_assets_filter, which presumably offers richer filtering, leaving overlap unresolved.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this versus ai_modeling_assets_filter or the canvas/collection/library list tools. Usage is only implied by the word "List"; no exclusions, prerequisites, or selection criteria are given.

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