Skip to main content
Glama
Sign In
Noves MCP Server

Noves MCP Server

Official
by Noves-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_token_price_comparison

Compare token price between two timestamps to show price change on a blockchain network.

Instructions

Compare token price between two timestamps to show price change

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>",
      "tokenAddress": "<tokenAddress>",
      "fromTimestamp": "<fromTimestamp>"
    },
    "name": "get_token_price_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesBlockchain network (e.g., ethereum, polygon, arbitrum)
toTimestampNoEnd Unix timestamp for comparison (default: current time)1786352238
tokenAddressYesToken contract address
fromTimestampYesStart Unix timestamp for comparison

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (comparing prices) but does not specify the output format, such as whether it returns a percentage, absolute difference, or a structured object. This is adequate but lacks detail on return value or potential side effects.

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?

The description is a single, focused sentence that conveys the essential purpose without waste. It is well-structured and front-loaded, making it easy for an agent to parse quickly.

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?

The tool has no output schema and no annotations, so the description must cover the essentials. It does explain the main purpose but omits details like the result format, units, or edge-case handling (e.g., equal timestamps). Suitable for a simple tool but not comprehensive.

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%, so the baseline is 3. The description adds minimal meaning beyond the schema—it only reinforces the 'between two timestamps' relationship. No additional parameter details are given, but the schema already documents each parameter sufficiently.

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?

The description clearly states the tool's function: comparing token price between two timestamps to show price change. This explicitly distinguishes it from sibling tools like get_current_token_price and get_historical_token_price, which do not involve comparison between two points in time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case: when users need to compare prices at two different timestamps. It does not explicitly name alternatives or exclusions, but the context is clear given the sibling tool names and the 'between two timestamps' phrasing. A brief mention of when not to use it would push it to 5.

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