Merkl MCP Server

APR Bins

opportunities-bins-apr

Retrieve Merkl opportunities grouped into APR bins, filtered by chain, token, status, type, APR/TVL thresholds, and campaigns to find relevant yield opportunities.

Instructions

GET /v4/opportunities/bins/apr

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 APR bins

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Sep 13, 2026

TDQS

C2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only GET but says nothing about authentication, pagination, rate limits, or what happens if filters are combined. This is only marginally better than no behavioral information.

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?

It is extremely short, but that brevity is under-specification rather than conciseness. There is no front-loaded explanation of what the tool does or how to interpret its output, so the single line does not earn its place as an effective description.

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?

For a 25-parameter endpoint with no annotations, the description is insufficiently complete. Although an output schema exists and the input schema has strong coverage, the description still fails to explain the tool's domain purpose, when it should be chosen over siblings, or how APR bins relate to the rest of the opportunities API.

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?

The input schema has 96% description coverage across 25 parameters, so the schema itself documents nearly all filter semantics. The description adds no parameter meaning beyond the schema, which is acceptable here because the schema does the heavy lifting.

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?

The description is only the raw endpoint path 'GET /v4/opportunities/bins/apr'. It restates the tool name/title rather than explaining what an APR bin is or what the tool returns. It does not help an agent distinguish it from sibling opportunities-bins-tvl or the aggregate tools.

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 at all. The description does not say when to use APR bins versus TVL bins, aggregate endpoints, or search endpoints, nor does it mention any prerequisites or alternatives.

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

Deploy Server