Skip to main content
Glama
Sign In
chainlink-sentinel

chainlink-sentinel

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sentinel_chain

Scan all Chainlink price feeds on a specific blockchain to monitor data accuracy and availability for DeFi applications.

Instructions

Scan all Chainlink price feeds on a specific chain

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>"
    },
    "name": "sentinel_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain to scan (ethereum, polygon, arbitrum, base, avalanche, bnb)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Scan' implies a read operation, the description fails to specify what the scan checks for (stale prices? deviations? updates?), whether it returns raw data or analysis, or any rate limiting concerns.

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?

Single sentence of nine words with clear subject-verb-object structure. No redundant phrases or unnecessary elaboration. Front-loaded with the action and target resource.

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?

Given the simple input schema (single enum parameter) and lack of output schema, the description covers the basic operation but remains incomplete regarding the scan's output format, return structure, or what specific conditions it checks for on the price feeds.

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 description coverage is 100% (the 'chain' parameter includes description and enum values). The description implies the chain parameter scopes the scan but adds no additional semantic detail, syntax constraints, or usage examples beyond the schema itself.

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?

Provides specific verb ('Scan'), resource ('Chainlink price feeds'), and scope ('on a specific chain'). However, it does not explicitly differentiate from sibling tools like sentinel_scan or sentinel_feed, leaving ambiguity about when to prefer this over tools with similar names.

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 no guidance on when to use this tool versus alternatives (e.g., sentinel_feed for specific feeds or sentinel_scan for generic scanning). No prerequisites or 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

Other Tools