Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_event_metadata

Fetch media and market metadata for a Kalshi event by event_ticker. Returns event and featured images, per-market colors/images, settlement sources, and competition context.

Instructions

Kalshi event metadata. Returns the media and market metadata for one Kalshi event by event_ticker. The response has the event image and featured image, a color code and image for each market, settlement sources with name and URL, and competition context when it applies. An unknown ticker returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
event_tickerYesKalshi event ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned payload (event/featured image, per-market color code and image, settlement sources with name/URL, competition context) and discloses the error behavior for an unknown ticker. It omits auth/rate-limit context but covers behavior meaningfully.

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?

Three tight sentences, front-loaded with the operation and resource, then payload details, then error behavior. No filler.

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?

No output schema exists, so the description must describe the return value, and it does so in useful detail, plus error handling. It is essentially complete for a single-parameter read tool, with only cross-sibling routing left unaddressed.

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 description coverage is 100%, so the single event_ticker parameter is already documented. The description adds only the framing that it identifies one event, which the schema implies, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Returns the media and market metadata for one Kalshi event by event_ticker'), so the agent knows exactly what comes back. It does not differentiate itself from close siblings like kalshi_event or kalshi_event_history, leaving the agent to infer the distinction.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement and no mention of alternatives. 'For one Kalshi event by event_ticker' implies intent, but the agent is not told when to pick this over kalshi_event or kalshi_event_history.

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