Skip to main content
Glama

DepthFeed

screener

Read-only

Cross-venue top-of-book snapshot for all assets across Polymarket, Kalshi, and Binance — a one-shot overview of the current state. No arguments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds value by specifying it is a cross-venue, top-of-book snapshot and a one-shot overview, providing context beyond structured fields.

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?

Single sentence with clear front-loaded purpose. Every word adds value; no wasted text.

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 no-parameter snapshot tool, the description covers scope and behavior. However, it does not describe the return format or data structure, which could be useful given no output schema.

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?

With 0 parameters and 100% schema coverage, the description simply states 'No arguments,' which is sufficient. Baseline for 0 params is 4, and the description adds clarity without redundancy.

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?

Description explicitly states it provides a cross-venue top-of-book snapshot for all assets across Polymarket, Kalshi, and Binance. This is a specific verb+resource and clearly distinguishes from sibling tools that target single venues or specific order books.

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

Usage Guidelines3/5

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

Description implies usage for a one-shot overview with no arguments, but does not explicitly state when to avoid using it or suggest alternatives like venue-specific order book tools. Usage context is inferred rather than stated.

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.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, clearly separated by venue prefix (kalshi_, limitless_, polymarket_) and action (get_orderbook, get_snapshots, search_markets). The screener and whoami tools are unique and not overlapping with any other tool.

Naming Consistency4/5

Most tools follow the venue_verb_noun pattern (e.g., kalshi_get_orderbook, polymarket_get_snapshots). However, polymarket_all_markets uses 'all' instead of a verb, and screener/whoami deviate entirely from the pattern, causing minor inconsistency.

Tool Count5/5

With 12 tools covering three venues plus cross-venue and session info, the count is well-scoped. Each tool serves a clear role without unnecessary bloat or deficiency.

Completeness4/5

The tool surface covers the core data retrieval operations (orderbook, snapshots, search, single market) for all venues. Missing are update/delete operations but those are outside the data provider scope. A minor gap is the lack of a dedicated 'get_market' for Kalshi and Limitless, though search_markets provides similar info.

Resources