Shelv MCP Server

Read Shelf File

read_shelf_file

Read-only

Retrieve a specific file from a Shelv shelf by providing the shelf identifier and file path to access its contents.

Instructions

Read a single file from a shelf

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": {
      "shelf_id": "<shelf_id>",
      "path": "<path>"
    },
    "name": "read_shelf_file"
  }
}

Input Schema

Name	Required	Description	Default
`shelf_id`	Yes
`path`	Yes

Output Schema

Name	Required	Description	Default
`path`	Yes
`bytes`	Yes
`content`	Yes
`shelf_id`	Yes
`truncated`	Yes
`content_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Feb 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, indicating a safe read operation, which the description aligns with by using 'Read'. The description adds minimal context beyond this, not detailing aspects like rate limits, authentication needs, or file format handling. With annotations covering the safety profile, a baseline score is appropriate, as the description adds little extra behavioral insight.

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 a single, efficient sentence with no wasted words, clearly front-loaded with the core action. It's appropriately sized for the tool's simplicity, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has annotations (readOnlyHint) and an output schema (which handles return values), the description's minimalism is somewhat acceptable. However, for a tool with 2 parameters and 0% schema coverage, it lacks details on parameter meanings and usage context, making it incomplete for full agent understanding without relying heavily on structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter details. The description mentions 'shelf' and 'file' but doesn't explain what 'shelf_id' or 'path' mean, their formats, or examples. It adds minimal semantic value beyond the schema, resulting in a baseline score due to incomplete compensation for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Read' and the resource 'a single file from a shelf', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_shelf_tree' or 'search_shelf', which might also involve reading shelf data, so it misses full sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'get_shelf_tree' for browsing or 'search_shelf' for finding files. It lacks any context on prerequisites, exclusions, or comparisons, leaving usage unclear.

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

Deploy Server