Meta-Stamp Pockets

by app.railway.up.metastampv3-production

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

Name	Required	Description	Default
`limit`	No	Maximum number of results to return per page. Defaults to 50, maximum 200 for catalog browsing.
`creator_id`	No	Optional filter to show only pockets from a specific creator. Use the creator's unique identifier.

TDQS

A4.7/5.0

Behavior5/5

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

Discloses auth requirement (Bearer token), pagination, and that it does not retrieve content. With no annotations provided, the description fully carries the behavioral disclosure burden.

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?

Four sentences each earn their place: purpose, usage, behavioral boundary, and auth/parameter context. Front-loaded and well-structured.

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?

Covers auth, pagination, filtering, return fields, and contrasts with siblings. No gaps for a simple list tool with optional parameters.

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 100% and the description adds no substantive parameter semantics beyond what schema already provides. Baseline 3 is appropriate.

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?

Clearly states 'List all available content pockets' and distinguishes from siblings by explicitly referencing search_pockets for specific topics and pull_content for retrieval.

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 when-to-use (browse full catalog, filter by creator) and when-not-to-use (prefer search_pockets for topics, pull_content for content retrieval) guidance.

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 tools Inspect

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 clearly distinct purpose: list_pockets for browsing the full catalog, search_pockets for discovery via filters, and pull_content for retrieving actual content. The descriptions explicitly cross-reference each other, eliminating ambiguity about when to use which.

Naming Consistency5/5

All three tool names follow a consistent verb_noun pattern (list_pockets, search_pockets, pull_content) with snake_case. This is a uniform and predictable naming convention.

Tool Count5/5

With 3 tools, the server is well-scoped for a content catalog service. Each tool covers a distinct step (browse, search, retrieve), and no tool is redundant or missing.

Completeness5/5

The tool surface covers the full discovery-to-retrieval workflow: browsing the catalog, searching by criteria, and pulling content. There are no obvious gaps for the stated purpose of accessing licensed content.

Resources

Need Help?