FortFi Treasury MCP

discover_tokens

Market-wide token discovery on a FortFi chain (USD). Use for trending/gainers/losers/volume/mcap — NOT the browser Explore REST route. Sorts: gainers_1d, gainers_30d, gainers_90d, gainers_365d, losers_1d, losers_30d, losers_90d, losers_365d, market_cap, volume_1d. No 7d or 30d-volume sort exists upstream — closest available gainers granularity to '1 week' is gainers_1d or gainers_30d; say so explicitly rather than silently picking one. Returns contract addresses for propose_swap / propose_bridge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chainId": "<chainId>"
    },
    "name": "discover_tokens"
  }
}

Input Schema

Name	Required	Description
`sort`	No	gainers_1d, gainers_30d, gainers_90d, gainers_365d, losers_1d, losers_30d, losers_90d, losers_365d, market_cap, volume_1d (default market_cap)
`limit`	No	Max results (default 10, max 25)
`query`	No	Optional name/symbol filter, e.g. 'USDC' or 'wrapped'
`chainId`	Yes	FortFi chain id, e.g. base-mainnet, ethereum-mainnet
`verifiedOnly`	No	Only verified tokens

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load; it discloses the ranked-list nature, the upstream limitation on available sorts, and that results include contract addresses usable downstream. It omits permission/auth requirements, rate limits, and pagination behavior beyond what the schema's limit field implies.

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

Conciseness5/5

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

Purpose is front-loaded in the first clause, then the tool's scope, the sort constraints, and the output handoff to propose_swap/propose_bridge follow in order. The sort list is long but is the tool's operative domain, so every sentence carries weight.

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

Completeness4/5

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

For a five-parameter read tool with no annotations and no output schema, the description covers scope, sort semantics, the notable upstream gap, and what the agent gets back (contract addresses). Auth and error behavior are the main uncovered areas, but that is a minor gap for this tool class.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real interpretive meaning for the sort parameter by mapping user intent (e.g. 'one week') onto the actually available granularities and telling the agent to state the substitution explicitly. The verbatim sort enumeration duplicates the schema and earns no credit.

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?

Names a specific verb and resource (market-wide token discovery) and scopes it to a FortFi chain with USD-denominated metrics, so the agent knows it returns ranked token lists rather than a single token lookup. It does not distinguish itself from the close siblings rank_tokens or screen_tokens, so it falls short of a 5.

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

Usage Guidelines4/5

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

Gives explicit when-to-use framing (trending/gainers/losers/volume/mcap) and an explicit exclusion (not the browser Explore REST route). It also warns that no 7d or 30d-volume sort exists upstream and instructs the agent to surface that rather than silently substituting. It stops short of routing to alternatives such as rank_tokens or screen_tokens for other screening needs.

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

All FortFi Treasury MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?