Merkl MCP Server

TVL Bins

opportunities-bins-tvl

Fetch Merkl opportunities grouped into TVL bins, then filter by chain, token, APR, status, or campaign to analyze liquidity and rewards.

Instructions

GET /v4/opportunities/bins/tvl

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Filter by name
`tags`	No	Filter by tag
`test`	No	Include opportunities with test campaigns
`type`	No	A comma separated list of Opportunity type
`point`	No	Include opportunities with point campaigns
`action`	No	A comma separated list actions. Legal values: POOL,HOLD,DROP,LEND,BORROW,LONG,SHORT,SWAP,INVALID
`search`	No	Search amongst multiple values (token, protocols, tags, campaigns)
`status`	No	A comma separated list of status. Legal values: LIVE,PAST,SOON
`tokens`	No	A comma separated list of token symbol. Use to filter by token
`chainId`	No	A comma separated list of chain ids. Example: ?chainId=1,42161
`chainName`	No	A comma separated list of chain names. Example: ?chainName=ethereum,arbitrum
`campaignId`	No	Search the opportunity linked to a given campaignId
`identifier`	No	Filter by identifier (mainParameter)
`maximumApr`	No	Maximum APR threshold
`maximumTvl`	No	Maximum TVL threshold in USD
`minimumApr`	No	Minimum APR threshold
`minimumTvl`	No	Minimum TVL threshold in USD
`tokenTypes`	No	Filter by token type. Use POINT to include point campaigns and PRETGE to include preTGE campaigns.
`creatorSlug`	No
`programSlugs`	No	A comma separated list of program ids or slugs. See GET /v4/programs
`creatorAddress`	No	Filter by creator address
`mainProtocolId`	No	A comma separated list of protocol ids. See GET /v4/protocols
`distributionTypes`	No	Filter by distribution type. Legal values: FIX_REWARD, MAX_REWARD, DUTCH_AUCTION
`rewardTokenSymbol`	No	Filter by opportunity with at least 1 campaign where the reward token has this symbol
`excludeSubCampaigns`	No	Exclude sub-campaigns from the results

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bins`	Yes	Distribution of opportunities across TVL bins

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Sep 13, 2026

TDQS

D1.4/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about read-nature, whether data is live or cached, granularity of TVL bins, ordering, or responses. An endpoint path is not a behavioral specification.

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?

The description is a single endpoint string with no structure. While short, it is not front-loaded with any useful information—it is under-specified rather than concise. It fails to earn its place as documentation.

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?

For a tool with 25 parameters and a sibling that handles APR bins, the description is wholly inadequate. It lacks purpose, usage context, and behavioral notes, leaving the agent to reverse-engineer intent from the name and schema. An output schema exists, so return values need not be described, but the description still fails to convey what the tool is for.

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 96%, so the schema documents the 25 filter parameters thoroughly with examples and legal values. Per the rubric, baseline 3 applies when schema coverage is high regardless of description content. The description adds no parameter meaning of its own.

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

Purpose1/5

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

The description is a bare REST endpoint string, 'GET /v4/opportunities/bins/tvl', which merely restates the tool name and reveals nothing about what the tool does beyond the HTTP verb. It does not describe what a TVL bin is, what data is returned, or how it differs from the sibling 'opportunities-bins-apr'. An agent cannot select this tool confidently from the description alone.

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

Usage Guidelines1/5

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

There is no usage guidance whatsoever. With 12 sibling tools including opportunities-bins-apr, opportunities-search, and opportunities-aggregate, the description provides no criteria for when to use this tool versus alternatives. The agent must infer everything from the name.

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

Deploy Server