records-vault

The four tools mostly serve distinct purposes: an about/pricing overview, reading a door grant, reading spec chapters, and verifying a receipt. read_door and verify_record have a mild overlap since read_door surfaces receipt ids that verify_record consumes, but the descriptions clearly explain their complementary roles.

Three tools follow a clear verb_noun pattern (read_door, read_spec, verify_record) in consistent snake_case. how_eformogi_works breaks the verb pattern by being a question phrase, a minor deviation but still readable.

Four tools is well-scoped for a narrow read-only records/verification server; each tool maps to a distinct operation and none feels redundant. The set is lean without obvious padding.

The surface covers the core read-only lifecycle: learn about the service, read a shared grant, read the spec, and verify a receipt. There is no discovery/listing operation for doors or records, but the per-grant credential model and receiver-agent framing make this a minor, intentional gap.