Merkl MCP Server

Count Opportunities

opportunities-count

Count Merkl opportunities matching filters like APR, TVL, status, chain, or token. Get the number of live, past, or upcoming reward campaigns for any query.

Instructions

GET /v4/opportunities/count

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
`campaigns`	No	Include campaign data. Will slow down the request
`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
`count`	Yes	Number of opportunities matching the filters

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Sep 13, 2026

TDQS

C2.1/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, yet it only supplies the HTTP method GET. This hints at a read-only operation, but it says nothing about authentication, rate limits, idempotency, or what the count represents.

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 extremely short, but it is under-specified rather than efficiently concise. A single endpoint path does not front-load useful information about purpose, filtering, or behavior.

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 26 optional filtering parameters, no annotations, and no output schema explanation in the description, a bare endpoint path is completely inadequate. An agent cannot tell when to use it, what it returns, or how it differs from sibling count or search tools.

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 input schema already documents nearly all 26 filter parameters thoroughly. The description adds no parameter meaning beyond the endpoint path, which is acceptable only 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 HTTP method and endpoint path, which essentially restates the tool name and title without explaining what is counted or how it relates to similar tools. It does not distinguish this count endpoint from siblings such as opportunities-search, opportunities-get, or opportunities-aggregate.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites, filtering intent, or expected context. The agent receives no explicit or implied usage rules beyond the endpoint name itself.

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

Deploy Server