Skip to main content
Glama

meta-stamp-pockets

by io.github.Christebob

list_pockets

List all available content pockets in the Meta-Stamp Pockets catalog, optionally filtered by creator. Use this tool when an AI agent needs to browse the full catalog or see everything available from a specific creator. Prefer search_pockets when looking for specific topics. Does NOT retrieve content — use pull_content with the returned pocket_id to access actual content. Requires a valid Bearer token. Optional creator_id parameter filters results to a single creator's pockets. Returns a paginated list of pockets with IDs, titles, descriptions, creators, content types, and pricing tiers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return per page. Defaults to 50, maximum 200 for catalog browsing.
creator_idNoOptional filter to show only pockets from a specific creator. Use the creator's unique identifier.

TDQS

A5/5.0
Behavior5/5

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

Despite no annotations, the description discloses key behavioral traits: requires Bearer token, returns paginated results, does not retrieve content. These details go beyond the schema and help the agent understand non-obvious constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the core purpose, and logically structured. Every sentence adds value—usage guidance, boundaries, auth, parameter details—without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (2 optional parameters, no output schema), the description covers all needed context: purpose, when to use, auth requirements, parameter details, and an important behavioral constraint (no content). It is fully complete.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds meaningful context: limit defaults to 50, max 200, and creator_id uses the creator's unique identifier. This aids correct parameter use beyond the raw schema.

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

Purpose5/5

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

The description clearly states the tool's purpose: to list all available content pockets, optionally filtered by creator. It distinguishes from sibling tools by explicitly recommending search_pockets for specific topics and pull_content for retrieving content.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool (browsing the catalog or viewing a creator's pockets) and when not (for specific topics, use search_pockets; for content retrieval, use pull_content). This helps the agent choose correctly.

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

All meta-stamp-pockets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a distinct purpose: listing all pockets, searching pockets, and pulling content. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase_with_underscores: list_pockets, search_pockets, pull_content.

Tool Count5/5

Three tools is ideal for a content catalog server: browsing, searching, and retrieving. Each tool serves a necessary role without bloat.

Completeness5/5

The tool set covers all essential operations for a consumer-facing content platform: discovery through listing and searching, and retrieval through pulling. No obvious gaps.

Resources