List the items in your TomeVault that this token can read. Requires a vault access token with the items:read scope. Encrypted (private) items are never listed.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral context: the scope requirement and the important detail that encrypted items are never listed. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler. First sentence states core purpose, second adds necessary scope and exception. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple single-parameter input and no output schema, the description covers the main purpose and a key behavioral exception. However, it doesn't mention that the result is a list of items or any pagination details. Still adequate for a straightforward list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning no parameter descriptions in the schema. The tool description does not mention the 'limit' parameter or its meaning (pagination control). Although the schema provides bounds, the description should compensate for the lack of schema descriptions, but it fails to do so.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb 'list' and resource 'items in your TomeVault', with explicit scope requirement and exception for encrypted items. Distinguishes well from siblings like get_vault_item (singular) and get_tome (single object).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit requirement for vault access token with items:read scope, and clarifies that encrypted items will never be listed. Does not explicitly mention alternatives, but the context of a list operation vs. single-item retrieval is implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
