get_taker
Taker portfolio. Volume bought, fulfilled intents, currency and platform allocations, daily activity, and recent intents for a taker wallet.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes |
peerlytics
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose behavioral traits such as read-only nature, side effects, or auth requirements. It only lists data fields without indicating safety or usage constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is a single sentence listing key data points; it is concise and to the point. However, it lacks structural elements like bullet points or separation of concerns.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one parameter and no output schema, the description is incomplete. It does not explain return format, pagination, or edge cases, leaving the agent with insufficient information for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage and no parameter documentation. The description mentions 'taker wallet' but does not explain the address parameter's format, purpose, or constraints, adding minimal value beyond the schema.
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?
Description clearly states it provides a taker portfolio and lists included data types (volume, intents, allocations, activity). It implicitly distinguishes from siblings like get_maker and get_taker_history by focusing on portfolio overview.
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 explicit guidance on when to use this tool versus alternatives. The description only implies usage for taker portfolio data, but does not mention prerequisites, limitations, or sibling tool differentiation.
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
C2.8/5.0
Disambiguation3/5
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.