Skip to main content
Glama

Get Item Catalog Page

horizon_get_item_catalog
Read-onlyIdempotent

Read a single page of item templates and archived catalog entries with keyset pagination for displaying item details or reviewing a catalog.

Instructions

Reads one bounded item template page, including archived templates. Use when: showing item details or reviewing a catalog with explicit keyset pagination. Not for: automatically scanning the whole catalog or combining pages from different revisions. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. Side effects: None (read only). Returns: {revision,definitions,nextAfterKey,total,limits,serverTime}. Retain the first revision for later pages; null cursor ends the list. Errors: 409 REVISION_CONFLICT or an uncertain response: use horizon_get_items and reconcile intent, never silently substitute a new revision and repeat. 404 ITEM_NOT_FOUND means this instance no longer exists. 422 ITEM_PROPERTY_NOT_ALLOWED/ITEM_PROPERTY_LIMIT_REACHED rejects the entire adjustment. 401 means the session is missing or expired: sign in again and retry with the new accessToken. 403 for a session means the token belongs to another user: pass the userId that signed in. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).

Input Schema

NameRequiredDescriptionDefault
limitNoExplicit page size, default 50; never automatically fetch all pages
userIdYesSigned-in player UUID matching the session
afterKeyNoPrevious nextAfterKey, or omit for the first page
sessionTokenYesPlayer accessToken sent only as Authorization Bearer
catalogRevisionNoFirst page revision, retained unchanged on later pages; conflict requires restarting the catalog read

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, yet the description adds real value: the sign-in prerequisite and how to pass the accessToken, the requirement to retain the first revision across pages, and a full error taxonomy including 401/403 session semantics and 429 rate limiting. The only gap is that it does not say whether archived templates are flagged in the payload, which matters for a read that includes them.

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

Conciseness3/5

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

Front-loaded with labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors) which is good structure, but the error block balloons to five status codes plus isError and rate-limit conventions, much of which is boilerplate that could be one line. It is informative but heavier than it needs to be for a single-page read.

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?

For a paginated read with no output schema, the description supplies the return shape {revision,definitions,nextAfterKey,total,limits,serverTime}, session/API-key prerequisites, pagination termination, and error recovery. An agent can call this correctly and recover from each documented failure without further information.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds lifecycle meaning the schema does not: catalogRevision must be retained unchanged across pages, a null cursor ends the list, and the limit is an explicit page size rather than a fetch-all. That is useful procedural semantics for both the cursor and revision parameters.

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?

States a concrete verb+resource+scope: read one bounded item template page, including archived templates. The 'Not for' clause separates it from whole-catalog scanning and from mixing revisions, and the error text routes the agent to horizon_get_items, so it is distinguishable from its siblings without opening 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 Guidelines5/5

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

Explicit 'Use when' (showing item details, catalog review with keyset pagination) and 'Not for' (auto-scanning the catalog, combining pages across revisions), plus an alternative path via horizon_get_items on 409 or an uncertain response. Nothing is left to inference.

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