peerlytics

get_market_summary

Market intelligence snapshot

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (default: 200, max: 500).
`cursor`	No	Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint.
`offset`	No	Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate.
`currency`	No	Repeatable or comma-separated currency codes.
`platform`	No	Repeatable or comma-separated platform ids (analytics treats as verifier alias).
`include_rates`	No	Include individual rate entries.

TDQS

D1.9/5.0

Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits (e.g., pagination behavior, rate limits, data freshness). The single phrase is entirely insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short but not concise—it is under-specification. The description should convey essential details, not just a vague label.

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

Completeness1/5

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

With no output schema and no annotations, the description is wholly inadequate. It provides no context about return values, pagination (despite cursor/offset params), or how filters affect results.

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 coverage is 100%, so parameters are well-documented in the schema. The description adds no value, but the baseline for high coverage is 3.

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

Purpose2/5

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

Description 'Market intelligence snapshot' is vague; lacks a specific verb and does not distinguish the tool's action (e.g., fetch, list). It gives little sense of what the tool returns.

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?

No guidance on when to use this tool versus siblings. Many sibling tools exist (e.g., get_analytics_summary, get_protocol_overview), but the description offers no context for selection.

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

All peerlytics tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Most get_* and list_* tools target distinct domain entities, but several high-level analytics endpoints overlap in purpose (get_analytics_summary, get_protocol_overview, get_market_summary, get_timeseries, get_leaderboard), and pairs like get_deposit/get_deposit_context and get_vault/get_vault_analytics create close boundaries. The descriptions clarify the differences, but an agent would need to read carefully to avoid misselection.

Naming Consistency5/5

The tool set follows a strong verb_noun pattern: get_ for single-entity or detail views, list_ for collections, plus explicit action endpoints like export_trade_log, plan_routes, and search_explorer. All names are snake_case and predictable, with no mixing of conventions.

Tool Count3/5

28 tools is on the heavy side for an MCP server, even for a broad analytics domain. Most tools map to real entities, but the surface is padded by overlapping summary/analytics endpoints and separate detail, context, and analytics variants for the same resources.

Completeness4/5

The server provides broad read-only coverage of the protocol domain: deposits, intents, makers, takers, vaults, delegates, verifiers, platforms, integrators, orderbook, routes, activity, and search. Minor gaps such as no list_vaults or list_integrators are workable via search/get endpoints, and mutating operations appear out of scope for an analytics-focused server.

Resources

Need Help?