Skip to main content
Glama

List uploaded assets

list_assets
Read-onlyIdempotent

List ready images in your VoxTale account. Use returned IDs as generation references: face = the creator's likeness, reference = must appear in every thumbnail unedited, style_ref = only shapes the look. Does not fetch external images.

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

Input Schema

NameRequiredDescriptionDefault
roleNo
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real context beyond that: only 'ready' images are returned and external images are not fetched. It says nothing about pagination behavior across limit/cursor, which is the main remaining behavioral gap.

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?

Three tight sentences, front-loaded with purpose and then the role semantics; no filler. The role enumeration is dense but each clause earns its place by disambiguating an enum value.

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?

An output schema exists so return shape need not be explained, and the read-only annotations are clear. However, for a tool with three parameters at 0% schema coverage, leaving 'brand', limit and cursor undefined means an agent must guess at filtering and paging semantics.

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 0%, so the description must carry the parameter burden, and it does partially: it defines face, reference and style_ref semantics with concrete behavioral consequences. It omits the 'brand' enum value entirely and says nothing about limit or cursor, leaving two of three parameters and one enum member undocumented.

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 and resource ('List ready images in your VoxTale account') with the qualifier 'ready', which conveys a filtering condition on top of the bare name. It does not name a sibling to contrast with, which matters given the confusingly similar 'list_asset_images' in the toolset, so it falls short of a 5.

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?

The description explains what to do with the results ('Use returned IDs as generation references') but never states when to call this instead of alternatives such as list_asset_images or list_generations. Usage is implied through the downstream purpose rather than through explicit selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources