Skip to main content
Glama
Sign In
chainlink-sentinel

chainlink-sentinel

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sentinel_compare

Compare price pairs across multiple blockchain networks to identify cross-chain deviations and ensure data consistency.

Instructions

Compare a price pair across all available chains to detect cross-chain deviations

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

Input Schema

NameRequiredDescriptionDefault
pairYesPrice pair to compare (e.g., BTC/USD, ETH/USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It adds valuable context about multi-chain scope and deviation detection purpose, but omits safety properties (read-only vs destructive), rate limits, or return value structure.

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 compact sentence with zero waste. Front-loaded with action verb, immediately communicates resource type, scope ('across all available chains'), and specific value proposition ('detect cross-chain deviations').

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 a single-parameter tool with complete schema coverage, but lacks output format specification. Mentions 'deviations' implying analytical output, but without output schema or annotations describing return structure, completeness is limited.

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 has 100% coverage with clear description and examples for the 'pair' parameter. Description mentions 'price pair' but doesn't add syntax details, validation rules, or format constraints beyond what the schema already provides. Appropriate baseline score for high schema coverage.

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 provides specific verb 'Compare', resource 'price pair', and distinctive scope 'across all available chains'. The deviation detection purpose clearly distinguishes it from siblings like sentinel_scan or sentinel_chain which likely perform different functions.

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?

Implies usage scenario (detecting cross-chain deviations) but lacks explicit when-to-use guidance, prerequisites, or comparisons to alternatives like sentinel_feed which might provide raw price data instead of deviation analysis.

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