Skip to main content
Glama

ai_modeling_library_user_items

Read-only

Lists model and collection cards accessible to a specified Studio creator by user ID, with pagination for browsing their library.

Instructions

List accessible model and collection cards for a specified Studio creator.

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": {
      "user_id": "<user_id>"
    },
    "name": "ai_modeling_library_user_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
page_sizeNo
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/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 safety is covered. The description adds one genuinely useful behavioral detail — results are limited to what is 'accessible' to the caller — but says nothing about pagination, result ordering, or volume, despite two pagination parameters.

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 well-formed sentence with no filler, front-loading the verb and resource. It is efficient but so terse that conciseness shades into under-specification.

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?

As a read-only list tool with no output schema, it needs only modest explanation, and the access scoping is stated. The missing pagination semantics for a paginated endpoint is the main shortfall.

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 carries the full burden. It only gestures at user_id ('specified Studio creator'), leaving page_size and page_token completely unexplained in both schema and description — the agent cannot tell how to page or what the defaults mean.

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?

Specific verb ('List') plus concrete resources ('model and collection cards') and a scope ('accessible ... for a specified Studio creator'). An agent knows what it returns, though the description never distinguishes it from library/assets listing siblings.

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?

No when-to-use or when-not-to-use guidance and no alternative named, even though siblings like ai_modeling_library_list and ai_modeling_assets_list plausibly overlap. The only hint at selection criteria is 'for a specified Studio creator', which the agent must infer means per-user filtering.

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