Skip to main content
Glama

TomeVault

by io.github.olijboyd
OverviewDiscussionsAdmin

Server Details

Check AI instruction files, look up a company's record, and keep a dated record of your own.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
16.9% over 43 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.9/5.0

Scored across 15 tools

Disambiguation2/5

Several tools overlap in purpose: get_tome and get_vault_item both fetch a single item's content without clarifying the relationship between tomes and vault items, and connect_source overlaps with get_workspace_status for reporting connected sources. The detailed descriptions help, but the boundaries between these pairs remain unclear.

Naming Consistency4/5

Most tool names follow a clear snake_case verb_noun pattern (get_tome, list_vault_items, scan_content, verify_attestation). There are minor deviations such as deliver_to_source with its preposition and connect_source whose name undersells its reporting behavior, but the overall convention is predictable.

Tool Count4/5

Fifteen tools is within a reasonable range for a workspace, content-management, and attestation service, and most tools map to a distinct concern. The count feels slightly heavy because a few tools (get_tome vs get_vault_item, connect_source vs get_workspace_status) could potentially be consolidated.

Completeness3/5

Read, search, scan, versioning, and delivery workflows are well covered, along with members, billing, and workspace status. However, there are notable lifecycle gaps: no disconnect/remove for sources, no remove or role-update for members, and no delete or explicit approve action for vault items/versions.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedissue_certificate2 fields changed
      • removedInput schema / properties / item_ids
        Removed value: -{
-  "description": "Ids of stored files in that client's folder, from list_vault_items.",
-  "items": {
-    "maxLength": 64,
-    "minLength": 1,
-    "type": "string"
-  },
-  "maxItems": 25,
-  "minItems": 1,
-  "type": "array"
-}
      • changedInput schema / required
        Previous value: -[
-  "client_id",
-  "item_ids"
-]New value: +[
+  "client_id"
+]
  2. 1 tool update
    • Addedissue_certificate
  3. 1 tool update
    • Addedlist_certifications
  4. 6 tool updates
    • Addedconnect_source
    • Addeddeliver_to_source
    • Addedget_billing_summary
    • Addedget_workspace_status
    • Addedinvite_member
    • Addedlist_members
  5. 1 tool update
    • Addedsave_vault_version
  6. 1 tool update
    • Addedverify_attestation
  7. 7 tool updates
    • First observedconvert_content
    • First observedget_provenance
    • First observedget_tome
    • First observedget_vault_item
    • First observedlist_vault_items
    • First observedscan_content
    • First observedsearch_tomes

Related MCP Connectors

Related MCP Servers

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