Skip to main content
Glama

Emercoin Agent

by io.github.emercoin

Read NVS record

read_record
Read-onlyIdempotent

Read one Emercoin NVS (Name-Value Storage) record by its full name — an agent's identity (ai:gh:<github_id>) or a memory (ai:gh:<github_id>:mem:<hash>) written by register_identity / store_memory. Returns the confirmed on-chain record, or a pending one still in the mempool — the status field ('confirmed' | 'pending') distinguishes them. Read-only, no sign-in required; use whoami to find your own github_id. Returns null fields for a name that does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull NVS record name to read. Identity records are 'ai:gh:<github_id>' (e.g. 'ai:gh:3772563'); memory records are 'ai:gh:<github_id>:mem:<sha256-hex>'. Any existing NVS name works.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
timeNo
txidNo
valueNo
statusNo
addressNo
pendingNo
operationNo
days_addedNo
pending_updateNo
address_is_mineNo

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint. The description adds valuable behavioral details: returns pending vs confirmed status, null fields for nonexistent names, no sign-in required. No contradiction with annotations.

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 paragraph that is relatively concise and front-loaded with the main action. It could benefit from slight restructuring (e.g., bullet points) but remains clear and efficient.

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 the presence of an output schema, the description does not need to detail return values. It covers purpose, name format, status distinction, null handling, sign-in requirements, and sibling guidance—complete for a simple read tool.

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?

Schema coverage is 100% and the schema's parameter description is thorough. The description adds further context with examples and links to identity/memory naming patterns, enriching understanding beyond the 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 clearly specifies the tool reads an NVS record by full name, describes record types (identity and memory), and links to sibling tools (register_identity, store_memory). It distinguishes itself as a read-only counterpart to write tools.

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 tells when to use the tool (to read a record by full name) and directs the agent to use 'whoami' to find a github_id. It does not explicitly state when not to use it, but the sibling context makes exclusion clear.

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