Skip to main content
Glama

ai_modeling_gallery_item

Read-only

Retrieves a gallery item by ID and returns the full detail view used by Studio, enabling agents to inspect an asset before editing, downloading, or managing it.

Instructions

Read a gallery item with the same full detail view used by Studio.

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": {
      "item_id": "<item_id>"
    },
    "name": "ai_modeling_gallery_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/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 adds that the response equals Studio's full detail rendering, which hints at response richness, but it says nothing about failure behavior for a missing or inaccessible item, or about any access/auth constraints implied by openWorldHint.

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 tight sentence with the core action front-loaded and no filler. It is efficient, though the brevity comes at the cost of the guidance the definition lacks.

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?

For a read-only, single-parameter getter with no output schema, the description is roughly adequate: annotations cover safety and 'full detail view' hints at the payload. However, the agent is left without the origin of item_id or any notion of the response shape, which matters because no output schema exists.

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?

There is one required parameter at 0% schema description coverage, so the description carries the burden and provides nothing: no explanation of the item_id format (the schema's restricted character pattern), no statement of where ids come from (presumably browse/search), and no example. It adds no meaning beyond the bare property name.

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 ('Read a gallery item') and adds scope ('same full detail view used by Studio'), which tells an agent this is a single-item detail fetch rather than a listing. It does not explicitly name the sibling list/search tools it contrasts with, so it falls short of full differentiation.

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: 'full detail view' suggests it should be chosen when complete information about one item is needed, versus browse/feed/search for discovery. There is no explicit when-to-use statement, no exclusion, and no mention of what to do when the id is unknown.

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