Skip to main content
Glama
Sign In
ChainHilt

ChainHilt

by bancorprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_chain_info

Retrieve chain details by chain name or chain ID to identify a supported EVM network before authorizing API requests or sending transactions.

Instructions

Get chain information for a chain name or id.

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

Input Schema

NameRequiredDescriptionDefault
chainIdNo
chainNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not clarify read-only behavior, permission requirements, error handling for unknown chains, or what happens when neither optional selector is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. Its brevity is appropriate in form, though the content is under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with two optional parameters and no annotations or output schema, the description should at least clarify selector precedence, defaults when neither parameter is supplied, and the kind of chain information returned. None of these are covered.

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

Parameters2/5

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

Schema description coverage is 0%, and both parameters are undocumented. The description implies chainName and chainId are alternative selectors, but it does not explain precedence when both are provided, accepted formats, or behavior when neither is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: retrieve chain information by chain name or ID. However, 'chain information' is vague about what data is returned, and it does not reference any sibling tools or scope boundaries.

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?

There is no guidance on when to use this tool rather than another, no preconditions, and no exclusions. The only implied usage is that it is for looking up a chain.

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