Skip to main content
Glama
MerariJafet

AGORA

by MerariJafet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agora_verify_tokoin_chain

Verify the TOKOIN blockchain independently: check block hash linkage and per-block research commitment Merkle roots instead of trusting external claims.

Instructions

Verify the TOKOIN block chain yourself instead of trusting this world.

Returns the chain verification: block hash-linkage and the per-block
`research_commitment_root`, the Merkle root committing to every research
reward and its `paper_hash`, `dataset_manifest_hash`, `code_manifest_hash`
and `genealogy_root`. Note what this proves and what it does not: the hashes
commit to bytes, never to correctness, authorship or truth.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does so well: it discloses the return semantics (hash-linkage, Merkle roots, the committed byte fields) and explicitly bounds what the verification proves ('the hashes commit to bytes, never to correctness, authorship or truth'). This epistemic caveat is exactly the behavioral context an agent needs; it only lacks an explicit read-only/no-side-effects statement.

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?

Front-loaded with the purpose, then the return contents, then the crucial limitation. Every sentence earns its place, though the middle sentence enumerating four hash fields is dense and could be tightened.

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

Completeness4/5

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

With an output schema present the description needn't enumerate return values, yet it does describe them while adding the non-obvious epistemic caveat the schema cannot convey. For a zero-param, no-annotation, output-schema-backed tool this is nearly complete; an explicit no-side-effects note would finish it.

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?

The tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate, and it correctly introduces none.

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?

States a specific verb ('Verify') and resource ('TOKOIN block chain') and articulates the exact scope of what is verified: block hash-linkage plus the per-block research_commitment_root. This distinguishes it clearly from the sibling agora_tokoin_status, which would report state rather than cryptographically verify the chain.

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

Usage Guidelines3/5

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

The phrase 'instead of trusting this world' implies the use case (independent trust-minimized verification) but never names the alternative sibling (agora_tokoin_status) or states explicit when/when-not conditions. Usage is implied rather than spelled out.

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

Deploy Server

Other Tools