Emer Ai Tools

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

Name	Required	Description	Default
`name`	Yes	Full 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

Name	Required	Description	Default
`name`	No
`time`	No
`txid`	No
`value`	No
`status`	No
`address`	No
`pending`	No
`operation`	No
`days_added`	No
`pending_update`	No
`address_is_mine`	No

TDQS

A5/5.0

Behavior5/5

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

The description adds context beyond annotations, explaining return states (confirmed vs pending) and behavior for non-existent names (null fields). Annotations already declare readOnlyHint, idempotentHint, openWorldHint; description adds valuable behavioral detail without 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?

The description is two sentences, each well-structured and informative. The first sentence states the core purpose, the second adds return format and usage hint. No wasted words.

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 tool's low complexity (one parameter), full annotations, and presence of output schema, the description covers all needed context: purpose, parameter format, return states, and alternative tool. It is complete.

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?

The description adds meaning beyond the input schema: it specifies name patterns for identity and memory records, provides examples, and clarifies scope. Schema description coverage is 100%, but description still enhances understanding.

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 states the tool reads one Emercoin NVS record by full name, clearly identifying the resource and action. It distinguishes from sibling tools like register_identity and store_memory by specifying that this tool is for reading only.

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?

The description explains when to use the tool: to read identity or memory records by full name. It provides guidance on finding one's own github_id via whoami, and implies when not to use (for writing or identity lookup).

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

All Emer Ai Tools tools Inspect

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 serves a distinct purpose: node health check, record reading, identity registration, memory storage, and session info. No overlapping functionalities.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (node_status, read_record, register_identity, store_memory), except whoami which is a common convention and still fits the style.

Tool Count5/5

With 5 tools covering node status, read, write identity/memory, and session, the scope is well-managed. No tool is redundant or missing for core functionality.

Completeness4/5

Core operations (check node, read, write identity/memory) are present, but missing listing/enumeration of records and an explicit sign-in tool are minor gaps.

Resources

Need Help?