Skip to main content
Glama

Tito MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List registrations (orders)

tito_list_registrations
Read-only

List an event's registrations — Tito's orders — newest first, with buyer name/email, reference, total, state, paid/refunded flags, discount code and ticket quantities. Filter by free text (email, name, slug, reference, company, discount code), state, and created/updated time. Cancelled ones are excluded unless states includes 'cancelled'. Tito: GET /:account/:event/registrations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search: email, name, slug, reference, company name or discount code.
pageNoPage number (page[number]), from 1.
sortNoSort attribute (search[sort]). Default created_at, newest first.
viewNoResponse view. Lists default to 'short'; 'extended' includes associated records but can be slow and large.
statesNoOnly these states (search[states][]).
directionNoSort direction (search[direction]).
page_sizeNoResults per page (page[size]), 1-1000. Tito's default is 100.
event_slugYesThe event slug (the second part of https://ti.to/<account>/<event>), e.g. 2026.
account_slugNoThe account slug (the first part of https://ti.to/<account>/<event>). Optional if TITO_ACCOUNT is set; tito_whoami lists the accounts this token can reach.
created_afterNoOnly registrations created after this time (search[created_at][gt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.
updated_afterNoOnly registrations updated after this time (search[updated_at][gt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.
created_beforeNoOnly registrations created before this time (search[created_at][lt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description still adds real behavior: newest-first default ordering, implicit exclusion of cancelled registrations, and which buyer/order fields come back. It doesn't discuss pagination limits or response size beyond what the schema's 'view' note already says.

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?

Front-loads the resource and ordering, then filters, then the default exclusion rule, then the upstream endpoint. Dense but every clause carries information; nothing is padded or restated from the schema.

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 12-parameter read tool with no output schema, the description usefully enumerates the returned fields and states default ordering and filtering so the agent knows what it gets. Pagination and the extended-view tradeoff live only in the schema, but those are covered there.

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 description coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the exact characteristics searchable via free text (email, name, slug, reference, company, discount code) and the non-obvious default that cancelled orders are hidden unless 'states' is set.

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 specific verb and resource ('List an event's registrations — Tito's orders') plus ordering ('newest first') and the returned field set, which clearly separates it from siblings like tito_list_refunds and tito_list_tickets. An agent can identify the tool 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 Guidelines4/5

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

Explains the default filter behavior (cancelled excluded unless 'states' includes 'cancelled') and the available filter axes (free text, state, created/updated time), which tells the agent when this tool fits. It stops short of explicitly naming an alternative tool or when *not* to use it.

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

All Tito MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources