FortFi Treasury MCP

get_token_chart

Fetch a compact Zerion chart summary plus deterministic EMA, RSI, MACD, Bollinger, return, max-drawdown, and data-quality analysis. Raw points are omitted by default; set includePoints:true only for visual charting or external analysis. Discontinuous pre-migration/launch samples are excluded from TA.

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": "get_token_chart"
  }
}

Input Schema

Name	Required	Description
`period`	No	Chart window (default day)
`address`	No	Token contract address or Solana mint (fallback)
`chainId`	Yes	FortFi chain id, e.g. base-mainnet, ethereum-mainnet
`fungibleId`	No	Zerion fungible id returned by discover_tokens (preferred)
`indicators`	No	Optional indicators to return; defaults to all. REST callers may pass a comma-separated value.
`includePoints`	No	Include the raw chart points array. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully explains that raw points are omitted by default, that includePoints should only be used for visual charting or external analysis, and that discontinuous samples are excluded from TA, though it does not discuss permissions, rate limits, or error behavior.

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?

The description is three tight sentences and front-loads the core purpose. It avoids wasted wording while still covering the most important behavioral caveats.

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 chart-analysis tool with no output schema, the description explains the return composition well: compact summary plus deterministic indicators and data-quality analysis. It could say more about output shape or error cases, but the essential contract is clear.

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 coverage is 100%, so the input schema already documents all six parameters thoroughly. The description adds useful meaning for includePoints and indicator computation exclusions, but it does not clarify the relationship between fungibleId and address beyond what the schema already states.

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

Purpose5/5

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

The description states a specific verb and resource: fetch a compact Zerion chart summary for a token, with deterministic technical indicators and data-quality analysis. It clearly distinguishes this from token discovery or ranking tools by focusing on chart and TA output.

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

Usage Guidelines3/5

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

The description gives conditional guidance for includePoints and notes that pre-migration/launch samples are excluded from TA, which implies appropriate use for normal chart analysis. However, it does not explicitly say when to prefer this tool over related sibling tools such as discover_tokens or rank_tokens, leaving cross-tool routing mostly implicit.

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?