Skip to main content
Glama
Sign In
Universal Crypto MCP

Universal Crypto MCP

by nirholas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

near_get_gas_price

Retrieve current gas price on NEAR. Optionally provide a block hash to query gas cost for a specific block; omit for the latest block.

Instructions

Get current gas price

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": "near_get_gas_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockIdNoBlock hash (omit for latest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only says 'Get current gas price.' It does not mention that blockId is optional, what units the gas price is in, or any other behavioral traits like potential rate limits or response format.

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 concise sentence with zero wasted words. It is appropriately sized for a simple getter tool and front-loads the core purpose immediately.

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?

For a trivial getter with one optional parameter and no output schema, the description is minimally adequate. It conveys the primary function, but lacks context about return values or the meaning of 'current' beyond the schema's blockId hint.

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?

The schema already provides a clear description for the only parameter (blockId), achieving 100% coverage. The description adds nothing extra about the parameter, so it meets the baseline for high schema coverage.

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?

The description 'Get current gas price' clearly states the action and resource with a specific verb. It is unambiguous, though it does not explicitly mention the NEAR chain, relying on the tool name for sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like sui_get_gas_price or aptos_estimate_gas. There are no prerequisites, exclusions, or alternative tool recommendations.

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