Skip to main content
Glama

Emercoin Agent

by io.github.emercoin

Store memory

store_memory

Anchor a memory/artifact on-chain as the NVS record ai:gh:<github_id>:mem:<content_hash> — a tamper-evident fingerprint others can verify later. Requires a signed-in session (OAuth) and counts against the FREE-tier per-minute write limit. Writes one NVS transaction paid by the gateway; reads back pending at once, confirmed after the next block (~10 min). Not idempotent — each distinct hash is a new record. Register your identity first. Returns the record name and the transaction id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metadataNoOptional JSON object stored with the record (note, source, tags, …). Omit if unused.
content_hashYesHash of the artifact/memory, e.g. a SHA-256 hex digest. It becomes the record's ':mem:<hash>' suffix; the content itself stays off-chain (e.g. IPFS) — only this fingerprint is anchored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
txidYes

TDQS

A5/5.0
Behavior5/5

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

Disclosures beyond annotations: not idempotent, each hash new record, returns pending then confirmed, counts against write limit, requires OAuth. No contradictions 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.

Conciseness5/5

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

Concise, well-structured with key information front-loaded. Every sentence adds value without 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 the complexity of on-chain writes, the description covers behavior, constraints, return values, and how it fits among siblings. Output schema exists, but description sufficiently explains outputs.

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

Parameters5/5

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

Schema has 100% coverage, but description adds meaning: content_hash is a SHA-256 hex digest and forms the record suffix; metadata is optional JSON for context. Explains the off-chain storage model.

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?

The description clearly states it anchors a memory/artifact on-chain as an NVS record with a specific naming pattern. It distinguishes from siblings like read_record (read) and register_identity (registration) by focusing on writing a tamper-evident fingerprint.

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 mentions prerequisites (signed-in session, identity registration) and constraints (write limit, non-idempotent, eventual confirmation). Provides when-to-use context without overloading.

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