BlindOracle

get_chainlink_price_feed

Retrieve Chainlink price feed data for any asset pair, with optional network selection.

Instructions

Get Chainlink oracle price feed data @requirement: REQ-CHAIN-001 - Price feed aggregation Properties: Alignment(+0.3), Autonomy(+0.2)

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": {
      "asset_pair": "<asset_pair>"
    },
    "name": "get_chainlink_price_feed"
  }
}

Input Schema

Name	Required	Description	Default
`network`	No		ethereum
`asset_pair`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations exist, so the description must convey behavioral traits. It only says 'Get ... data', implying read-only but not explicitly stating read-only or any side effects. The added 'Properties' line is not standard behavioral information and may confuse.

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 includes non-standard metadata that is not helpful for the agent. It is under-specified, sacrificing completeness for brevity.

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?

Given the lack of parameter descriptions and no behavioral context, the description is incomplete despite having an output schema. It does not provide enough information for correct invocation.

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

Parameters1/5

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

The input schema has 0% description coverage, meaning no parameter descriptions. The tool description adds no meaning to the parameters (e.g., what 'asset_pair' format, what 'network' options). This fails to help the agent with parameter usage.

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 'Get Chainlink oracle price feed data', which clearly identifies the action (get) and resource (price feed data). It distinguishes from siblings as no other tool is specifically for Chainlink oracle data. However, the inclusion of irrelevant metadata ('@requirement' and 'Properties') slightly detracts from clarity.

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?

No usage guidelines are provided. The description does not explain when to use this tool versus alternatives, nor does it give any context on prerequisites or scenarios.

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