Skip to main content
Glama

Niche of One Network

My OneReader library

reader_library
Read-onlyIdempotent

Members. The OneReader library on this account: purchases, your own files (titles only), shelves, tags and continue reading, with positions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reader_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly this tag.
shelfNoOnly this shelf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful scope by listing included data and noting own files are 'titles only' and positions are included, but it says nothing about pagination, limits, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is appropriately short, but the leading 'Members.' is a stray fragment that does not earn its place and makes the opening read like a heading or typo. The content sentence is dense but somewhat list-like; structure could be tighter.

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?

For a simple read-only listing tool with two fully documented optional filters, the description covers what data is included. However, with no output schema it does not describe the return shape or pagination, and it omits how the tag or shelf filters affect results.

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 100%, with both optional filters ('Only this tag' and 'Only this shelf') documented in the schema. The description does not mention tag or shelf filtering at all, so it adds no meaning beyond the schema; the baseline 3 is appropriate.

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 identifies the resource as 'The OneReader library on this account' and enumerates the content returned (purchases, own files, shelves, tags, continue reading with positions). It lacks an explicit verb and never differentiates from similarly named library tools, so it is clear but not sibling-aware.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as other library tools. The only implied usage is retrieving library contents; it does not say when tag or shelf filters should be used or when another tool would be preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources