Skip to main content
Glama

Emercoin Agent

by io.github.emercoin

Who am I

whoami
Read-onlyIdempotent

Report the current session's identity. Read-only, no sign-in required: an anonymous session gets {authenticated: false} with a hint (not an error), a signed-in one gets {authenticated: true} plus the GitHub-rooted id, login and tariff. Call it to confirm who you are before register_identity / store_memory; an anonymous caller must sign in (GitHub OAuth) first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
tariffNo
github_idNo
github_loginNo
authenticatedNo

TDQS

A5/5.0
Behavior5/5

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

Description explains read-only nature, no sign-in required, and response details for anonymous vs authenticated sessions. This adds substantive context beyond annotations (readOnlyHint, idempotentHint).

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: only three sentences. First sentence states purpose, second details response, third provides usage guidance. No extraneous information.

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 simplicity (no parameters, output schema likely covers response), the description is complete. It covers purpose, behavior, and usage context.

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?

No parameters; description clarifies that the tool returns identity info without needing input, adding value beyond the empty 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?

The title 'Who am I' and description 'Report the current session's identity' clearly indicate the tool's purpose. It distinguishes itself from siblings by specifying it's a read-only identity check, contrasting with register_identity and store_memory.

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?

Explicit guidance: 'Call it to confirm who you are before register_identity / store_memory; an anonymous caller must sign in (GitHub OAuth) first.' Clearly states when and how to use.

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