Skip to main content
Glama
Sign In

records-vault

by com.eformogi
OverviewDiscussionsAdmin

Read a shared door's facts

read_door
Read-onlyIdempotent

Read the facts sheet behind one door grant a student shared: the door, the sums, the lines, the plain text, the page link if there is one, and the receipt id on any item that carries one, for a receiver's own agent to hand to verify_record. No login, no API key: the grant itself is the credential, and it unlocks exactly one door. An expired, revoked, or malformed grant refuses with the same plain message every time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grant": "<grant>"
    },
    "name": "read_door"
  }
}

Input Schema

NameRequiredDescriptionDefault
grantYesThe door grant a student shared, starting with efgdg_.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, it explains the auth model: no login or API key, the grant itself is the credential, and it unlocks exactly one door. It also discloses uniform refusal behavior for expired, revoked, or malformed grants, which is valuable behavioral context.

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?

The purpose is front-loaded before the field list, and the second sentence covers auth and failure behavior without repetition. The first sentence is dense with enumerated fields, but every part earns its place.

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 one-parameter read tool with no output schema, the description covers what is returned, how authorization works, the one-door scope, and the failure mode. Nothing an agent needs in order to call it correctly is missing.

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%, so the schema already documents the single grant parameter and its prefix. The description adds useful meaning by framing the grant as a one-door credential and noting that no separate login or API key is needed.

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?

It states a specific verb and resource: read the facts sheet behind one door grant, and enumerates exactly what the sheet contains. It also scopes access to exactly one door and signals the handoff to verify_record, distinguishing it from the surrounding tools.

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

Usage Guidelines4/5

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

The intended use is clear: a receiver's own agent reads the shared door facts so it can hand them to verify_record. It does not explicitly say when to prefer read_spec or how_eformogi_works instead, but the context and handoff make the role unambiguous.

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