Feegate AI Agent data marketplace catalog & platform metrics

tech-indicators.indicator_now

Ask "what do the technical indicators say" — free: price, trend, RSI14 state, position in 60-bar range. ｜免费档：最新价、趋势判定、RSI14 与 RSI 状态、现价在近 60 根 K 线区间中的位置。参数 symbol / interval / limit / exchange 可选。

[zh] 供应方资产「技术指标快照（均线/MACD/RSI/ATR）」免费（每日限额按调用方计）。入参：symbol、interval、limit、exchange。 [en] Vendor asset "技术指标快照（均线/MACD/RSI/ATR）". Free (daily per-caller quota). Args: symbol, interval, limit, exchange. 付款/支付头在 MCP 请求头里带（X-Payment / X-Payment-Tx / Authorization: Bearer fg_…），不要放进参数。

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": {
      "symbol": "<symbol>"
    },
    "name": "tech-indicators.indicator_now"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`symbol`	Yes
`exchange`	No
`interval`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description does add genuinely non-obvious operational context: a daily per-caller free quota and the fact that payment must travel in MCP headers (X-Payment / X-Payment-Tx / Authorization: Bearer) rather than as arguments. It omits quota exhaustion behavior, error shapes, data freshness/bar-close semantics, and which exchange is assumed, so it is helpful but not complete for an unannotated tool.

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 same argument list is restated twice in different blocks, and the zh/en vendor lines duplicate the English opening, so the definition is padded with redundancy. The useful facts (returned fields, free quota, payment headers) are buried behind promotional framing and mixed-language repetition rather than front-loaded.

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?

With no output schema and no annotations, the description is the only source of truth, and it does enumerate the returned fields, which is a real plus. However, it leaves core call semantics undefined — what values interval accepts, what limit counts, which exchange defaults apply, and what happens when the free quota is exhausted.

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

Parameters2/5

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

Schema coverage is 0%, so the description must define the parameters, yet it only lists the names symbol/interval/limit/exchange with no accepted interval strings, limit range, or exchange identifiers. It also describes all four as optional while the schema requires symbol, which could mislead an agent into omitting a required argument.

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?

The description states a concrete resource and its free-tier payload: latest price, trend verdict, RSI14 state/condition, and where price sits inside the last 60 bars — an agent can tell what it will get back. It never mentions the sibling tech-indicators.indicator_report, so the agent cannot distinguish 'now' from 'report' from the definition alone.

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 lead phrase 'Ask "what do the technical indicators say"' implies a natural triggering question, which is mild usage guidance. There are no explicit when-not-to-use conditions, no pointer to indicator_report for deeper or historical analysis, and no note on which symbol/exchange conventions to prefer.

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

All Feegate AI Agent data marketplace catalog & platform metrics 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.