Skip to main content
Glama

Emercoin Agent

by io.github.emercoin

Node status

node_status
Read-onlyIdempotent

Report the Emercoin node's version, block height, header height, peer connections and sync state (synced true once block == header height). Read-only, no sign-in required, no parameters. Call it first in a session to confirm the node is healthy and fully synced before trusting read_record or writing with register_identity / store_memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
blocksNo
syncedNo
headersNo
versionNo
connectionsNo
verificationprogressNo

TDQS

A4.9/5.0
Behavior5/5

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

Discloses read-only nature, no sign-in required, and specific output fields (sync state). Complements annotations (readOnlyHint, openWorldHint, idempotentHint) with concrete behavior details. No contradiction.

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?

Two concise sentences. First sentence states purpose and outputs. Second provides usage guidance. Every sentence earns its place; no redundancy.

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

Completeness5/5

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

Given zero parameters, rich annotations, and existing output schema, description fully covers all needed context. Includes return values, usage timing, and relationship to sibling tools.

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

Parameters4/5

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

No parameters in schema, schema coverage 100%. Description explicitly confirms no parameters and adds usage context (no sign-in required). Baseline 4 is appropriate as description adds value beyond schema.

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 uses specific verb 'report' and lists exact data points (version, block height, header height, peer connections, sync state). Clearly distinguishes from sibling tools like read_record and register_identity by focusing on node health.

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

Usage Guidelines5/5

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

Explicitly advises calling this tool first in a session to confirm node health before using other tools. States conditions (synced state block == header height) and lists read_record, register_identity, store_memory as dependent operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Emercoin Agent toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: node_status for health, read_record for reading NVS records, register_identity for identity creation, store_memory for anchoring artifacts, and whoami for session info. No overlap.

Naming Consistency5/5

All tools use consistent snake_case naming with a verb_noun pattern (node_status, read_record, register_identity, store_memory) except whoami, which is a standard term. The pattern is predictable and clear.

Tool Count5/5

With 5 tools, the set is well-scoped for the server's purpose of interacting with Emercoin's Name-Value Storage. Each tool provides essential functionality without bloat or deficiency.

Completeness4/5

The tool set covers the core workflows: node health check, reading records, identity registration, memory storage, and session management. Missing delete or update tools, but given the immutable blockchain context, these are not critical gaps.

Resources