Skip to main content
Glama

ai_modeling_gallery_feed

Read-only

Browse the Studio gallery feed page by page using a continuation token, with adjustable page size for loading more gallery items.

Instructions

Browse the Studio gallery feed using its continuation token.

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

Input Schema

NameRequiredDescriptionDefault
page_sizeNo
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the notion of continuation-token paging; it says nothing about feed ordering, freshness, whether results are personalized, or what happens when the token is empty or expired, which are the behaviors an agent actually needs here.

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 short sentence with no filler, and the resource is front-loaded ahead of the paging mechanism. It is efficient, though the terseness is partly under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should carry more of the burden of explaining what the feed returns and how to advance through it. For a paginated, open-world list tool it leaves out result shape, token provenance and termination conditions, which is a substantial gap for correct invocation.

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 is the only place parameter meaning could be added, and it contributes almost nothing. It alludes to a continuation token but never constrains its format, lifetime or how it interacts with page_size, nor does it document the page_size bounds (1-100, default 20).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a verb ("Browse") with a resource ("the Studio gallery feed"), so the general intent is legible. However, it names no distinguishing scope versus the sibling ai_modeling_gallery_browse or ai_modeling_gallery_search, so an agent cannot tell which of these listing tools this one is for without inspecting the schema.

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?

"using its continuation token" hints that this is the paging follow-up to an initial browse, which is a small piece of guidance. There is no explicit statement of when to pick this over ai_modeling_gallery_browse or ai_modeling_gallery_search, and no prerequisites or exclusions 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