chainlink-sentinel

sentinel_feed

Read real-time Chainlink price feed data for cryptocurrency pairs across multiple blockchain networks to monitor market prices.

Instructions

Read a single Chainlink price feed (e.g., BTC/USD on ethereum)

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": {
      "chain": "<chain>",
      "pair": "<pair>"
    },
    "name": "sentinel_feed"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain name
`pair`	Yes	Price pair (e.g., BTC/USD, ETH/USD, LINK/USD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided. While 'Read' implies a safe, non-destructive operation, the description fails to disclose what data is returned (price, timestamp, decimals, roundId), network latency considerations, or error behavior when feeds don't exist.

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

Conciseness4/5

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

Single sentence is front-loaded with the action verb. While efficient, it may be overly terse given the absence of annotations and output schema—lacks structural elements like 'Returns...' or 'Use when...' that would help agent selection.

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

Completeness3/5

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

Adequate for the simple 2-parameter input schema, but incomplete given no output schema exists. For a data retrieval tool, the description should specify what constitutes a Chainlink price feed response (current price, updatedAt, answeredInRound) to set agent expectations.

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% with clear descriptions for both 'chain' and 'pair' parameters. The description provides a combined usage example (BTC/USD on ethereum) that illustrates the relationship between parameters, but adds minimal semantic value beyond what the schema already documents.

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?

States specific verb ('Read') and resource ('Chainlink price feed'), with 'single' distinguishing it from sibling comparison/scan tools. However, lacks explicit differentiation from sentinel_chain or sentinel_stablecoins.

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?

Contains only an inline example (BTC/USD on ethereum) with no explicit guidance on when to use this versus siblings like sentinel_compare or sentinel_scan. No prerequisites or error conditions mentioned.

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

Deploy Server