Skip to main content
Glama
Sign In
chainlink-sentinel

chainlink-sentinel

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sentinel_scan

Monitor Chainlink oracle performance across multiple EVM chains by scanning price feeds, detecting anomalies, and checking data staleness.

Instructions

Run a full cross-chain Chainlink oracle scan across 6+ EVM chains. Returns all feed prices, staleness, and detected anomalies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sentinel_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, description carries full disclosure burden. It adequately discloses return values (feed prices, staleness, anomalies) and geographic scope (6+ chains), but omits operational traits like execution duration, rate limits, authentication requirements, or whether results are cached vs real-time.

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?

Two tightly constructed sentences with zero waste. First sentence establishes action and scope; second discloses return values. Information density is high with no filler words or redundant phrasing.

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?

Compensates well for missing output schema by detailing return data types (prices, staleness flags, anomalies). However, lacks specifics on the '6+' chain identities, response format structure, or pagination behavior for what is likely a large data set.

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

Parameters4/5

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

Zero parameters present, establishing baseline score of 4. Description correctly implies no configuration needed for the cross-chain scope, though it could explicitly confirm 'no parameters required' for absolute clarity.

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?

Description uses specific verb 'scan' with clear resource 'Chainlink oracle' and scope 'across 6+ EVM chains'. The term 'full cross-chain' effectively distinguishes this from siblings like sentinel_chain (likely single chain) and sentinel_feed (likely specific feed).

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?

Provides implied usage through 'full' suggesting comprehensive analysis, but lacks explicit guidance on when to use vs alternatives like sentinel_feed for targeted checks or sentinel_compare for differential analysis. No exclusion criteria or prerequisites 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