Skip to main content
Glama

Mdexa

Get the Mdexa Ledger head

get_ledger_head
Read-onlyIdempotent

Latest signed head of the Mdexa Ledger (size, Merkle root, time, Ed25519 signature, public key). It proves what the ledger held at that time, not that a license conclusion is right. Not counted as a call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ledger_head"
  }
}

Input Schema

NameRequiredDescriptionDefault
hintsNo

Output Schema

NameRequiredDescriptionDefault
headNo
signatureNo
public_key_pemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds value beyond that with the quota behavior ('not counted as a call') and an epistemic caveat about what the result does not prove. It does not cover freshness/latency or whether the head can be stale, which would have made it a 5.

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?

Three short sentences, front-loaded with what the tool returns, then the interpretive caveat, then the quota note. Nothing is padded or repeated from the schema.

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?

An output schema exists, so return values need no prose explanation, and annotations carry the safety profile; the description covers purpose, interpretation and cost. The only real gap is the undocumented 'hints' parameter, which is the one thing an agent must still guess at.

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

Parameters2/5

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

The single parameter 'hints' (enum on/off) has 0% schema description coverage and is never mentioned in the description, so the agent has no idea what toggling it does. With coverage below 50% the description is expected to compensate, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the Mdexa Ledger head) and enumerates the returned fields (size, Merkle root, time, Ed25519 signature, public key), so an agent knows exactly what it gets. It stops short of naming the sibling it is not (e.g. get_ledger_proof), leaving differentiation to be inferred from the phrase 'latest signed head'.

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 line 'It proves what the ledger held at that time, not that a license conclusion is right' implies the intended use (verify ledger state) and hints that license questions belong elsewhere, but no alternative tool is named and no explicit when-to-use trigger is given. 'Not counted as a call' is a useful cost note but is not guidance on selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.