Skip to main content
Glama

Listing kit

get_listing_kit
Read-onlyIdempotent

Use when someone wants to list, write or settle a prediction market on a Tickerz index. A market on the index's next print, ready to paste, for LAYOFFS, MINTS: question (one sentence, with {strike} left to fill from strikes), period (the next UTC day, or the week ending the Saturday named, that has not begun), strikes (the 10th, 30th, 50th, 70th and 90th percentiles of the last 30 published numbers, two significant digits, equal ones listed once, null under 14 prints), settle_time_utc (when that period's number is expected to be published; null for the weekly index, where settle_rule gives the window), settle_rule (the number as first published, in column settlement_value of the settlement file; a later revision never changes it), tie_rule (a print equal to the strike resolves No), fallback, precision, grade and rulebook from the index's rulebook, source_url, settlement_file (CSV), mirror_file (the same file on a public mirror), proof (the daily OpenTimestamps proof), recount (the commands that recount a print from the chain; null where none exists), next_print_at, license, and paste: the whole market as plain text under 600 characters. Any other index returns no_kit with the reason. Same data as GET /api/indices/{ticker}/listing.json. Showing a number is free; settling real money on it is licensed: https://tickerz.com/pricing. Not advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_listing_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesIndex ticker, with or without the dollar sign: LAYOFFS, MINTS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Index ticker, with or without the dollar sign: LAYOFFS, MINTS, GIGS, WAGE"New value: +"Index ticker, with or without the dollar sign: LAYOFFS, MINTS"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds substantial context beyond annotations: the exact fields returned, the paste format (plain text under 600 characters), the licensing note ('showing a number is free; settling real money on it is licensed'), and the error mode for unsupported indices. It does not cover rate limits or authentication requirements.

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?

The description is one very long sentence with many semicolon-separated clauses. While it is front-loaded with the use case and every clause describes a returned field, the dense enumeration makes it harder to scan than a structured list. It earns its length because no output schema exists, but the run-on structure reduces clarity.

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?

Given one parameter, no output schema, and rich annotations, the description is largely complete: it explains the returned fields, the paste format, the licensing condition, and the failure case for unsupported indices. It does not mention rate limits, authentication, or what happens if the ticker is malformed beyond 'no_kit', but those gaps are minor for a read-only tool.

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 the schema already documents the single ticker parameter fully. The description adds meaning beyond the schema by stating that unsupported indices return no_kit with the reason, and it implicitly confirms which indices are supported (LAYOFFS, MINTS). Baseline would be 3, but this additional behavior earns a 4.

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

Purpose4/5

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

The description states a specific verb+resource: 'Use when someone wants to list, write or settle a prediction market on a Tickerz index.' It clearly describes what the tool returns (a ready-to-paste market kit with enumerated fields). It does not explicitly distinguish itself from siblings like get_index or get_question, so it falls short of a 5.

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 gives a clear when-to-use context ('when someone wants to list, write or settle a prediction market on a Tickerz index') and an exclusion behavior ('Any other index returns no_kit with the reason'). It does not name alternative tools or say when not to use this tool in favor of a sibling, so it is not a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources