Skip to main content
Glama

Niche of One Network

Read my library

read_library
Read-onlyIdempotent

Members. Read a product from your own Niche of One library: contents, one section, or a search inside it. Long text: best shown to the user as a document or artifact.

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": {
      "product": "<product>"
    },
    "name": "read_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
productYesProduct slug or title, as my_library lists it.
sectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the description's job is lighter; it adds a membership/access requirement and, more usefully, output guidance that long content should be surfaced as a document or artifact. It does not state whether a missing product errors or returns empty, which keeps it below a 5.

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

Conciseness4/5

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

Two compact sentences, front-loaded with the capability and mode list, with the output-formatting note last. The leading "Members." fragment is terse to the point of ambiguity, costing a point on clarity.

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 3-parameter read tool with no output schema, the description covers the modes and how to present long results, which is the important part. It still leaves the interaction between `query` and `section` unexplained and says nothing about what a successful read returns at the structural level.

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 coverage is only 33% — only `product` is described — so the description must compensate for `query` and `section`. It gestures at them via "one section, or a search inside it," but never states whether section is 1-based, whether query and section are mutually exclusive, or whether query searches the whole product or a single section.

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?

"Read a product from your own Niche of One library" gives a concrete verb and a scoped resource, and the enumeration "contents, one section, or a search inside it" distinguishes three read modes. It falls short of a 5 because it never names the listing sibling (my_library) that the product slug comes from, so the pairing is only implied.

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

Usage Guidelines3/5

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

The three modes imply when each capability applies, and "Members." hints at an access precondition, but there is no explicit when-to-use/when-not guidance and no routing to my_library or read_serial. The agent must infer that my_library is the way to discover valid product slugs.

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