Skip to main content
Glama
Sign In

records-vault

by com.eformogi
OverviewDiscussionsAdmin

Read the open record standard

read_spec
Read-onlyIdempotent

Read the open Eformogi record standard published at /spec. With no chapter, lists every published chapter. With a chapter slug, returns that chapter's markdown text.

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": "read_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
chapterNoA chapter slug from the list (e.g. "record-model", "verification", "issuing"). Omit to list every chapter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

While annotations handle the 'readOnly' safety profile, the description provides crucial behavioral context by defining the source location ('published at /spec') and the exact outputs (list vs. markdown text), which goes beyond basic schema definition.

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 highly efficient. It combines the definition, the source, and the two functional modes into two focused sentences without any redundant 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?

For a tool of this scope, the description is complete. It defines the resource, the input mechanism, and the resulting behavior, making it easy for an agent to invoke it correctly for both listing and retrieving.

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?

Schema coverage is 100%, meeting the baseline standard. Furthermore, the description adds value by specifying that the input is a 'slug' and provides concrete examples (e.g., 'record-model'), adding semantic context beyond the schema's type definition.

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 identifies the resource (the 'open Eformogi record standard') and provides a clear verb ('Read'). It specifies its scope by defining the two available modes: listing all chapters or retrieving a specific chapter.

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?

It explicitly dictates the usage based on input: omitting the 'chapter' parameter triggers a comprehensive list of all chapters, while supplying a 'chapter slug' triggers the retrieval of specific markdown text.

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

All records-vault toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources