Skip to main content
Glama
Sign In
ChainHilt

ChainHilt

by bancorprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mcp_status

Check local wallet addresses and identify missing configuration to verify MCP readiness before authorizing API requests or signing on-chain actions.

Instructions

Show local MCP wallet addresses and missing configuration.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; "Show" plus "status" implies a safe read with no mutation, which is useful. However, it does not state whether the tool requires prior authorization, whether it reads on-chain or from local config only, or how sensitive the exposed addresses are.

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?

A single front-loaded sentence that names the two outputs and stops, with no filler or restatement of the tool name. Nothing can be trimmed without losing information.

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 zero-parameter, zero-annotation tool with no output schema, the description must carry the whole burden of describing what comes back, and it only gestures at "addresses" and "missing configuration" without explaining the shape or meaning of either. It is serviceable for selection but leaves the agent guessing about the response.

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?

This tool takes zero parameters, so there is no parameter meaning for the description to add and the schema imposes nothing. With no parameters needed, the description adequately signals that the call takes no arguments, even though it does not say so explicitly.

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?

"Show local MCP wallet addresses and missing configuration" pairs a concrete verb with two specific resources, so the agent knows this returns address data plus a configuration gap report. It is reasonably distinguishable from wallet_balance and wallet_setup, though it never names those siblings to sharpen the boundary.

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?

The description states what is shown but never says when to reach for this tool versus wallet_setup or wallet_balance, and offers no prerequisites or exclusions. The only hint at usage is the phrase "missing configuration," which implies a diagnostic/troubleshooting context but leaves it for the agent to infer.

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