Skip to main content
Glama
chrischall

zola-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_registry

Read-only

Fetch registry items with purchase state, including requested and purchased quantities, fulfillment status, and availability. Supports pagination via limit and offset.

Instructions

View the couple's registry items with derived purchase state per item (requested_qty, purchased_qty, marked_fulfilled, availability, inconsistent). Paged via limit/offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return. Default 100
offsetNoItem offset. Default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv1.10.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max items to return. Default 100",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Item offset. Default 0",
+  "type": "number"
+}
  3. First observedv1.4.2

TDQS

A4.2/5.0
Behavior4/5

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

The description states that purchase quantities and fulfillment status are 'derived,' signaling that these fields are computed rather than raw stored values, and it discloses pagination via limit/offset. These details go beyond the readOnlyHint annotation, which only establishes safety. No contradiction with the annotation.

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?

A single sentence front-loads the main action and resource, then packs the derived fields in parentheses and ends with pagination. No filler or repetition.

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

Completeness4/5

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

For a simple read tool with no required parameters and no output schema, the description gives enough: it lists the notable derived fields and confirms pagination. It omits a full response shape, but the listed fields plus the schema defaults are sufficient for an agent to call it correctly.

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?

With 100% schema description coverage for limit and offset, the schema already documents both parameters. The description adds only the high-level 'Paged via limit/offset' note, which reinforces rather than extends the schema. Baseline 3 applies.

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 opens with the verb 'View' and a precise resource, 'the couple's registry items,' and then specifies the distinguishing output: derived purchase state per item. This clearly separates it from mutation siblings like add_registry_item and update_registry_item.

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

Usage Guidelines4/5

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

It establishes a clear use case: retrieve registry items along with derived purchase-state fields, and the paging behavior is stated. However, it does not explicitly contrast itself with related read tools such as get_gift_tracker or reconcile_registry, so the when-to-use guidance is implied rather than explicit.

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