Skip to main content
Glama

Niche of One Network

My library

my_library
Read-onlyIdempotent

Members. List the Niche of One products this signed-in member owns, plus titles their plan or pass includes, and which can be read here.

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": "my_library"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description's job is to add scope and content. It does: results are scoped to the signed-in member, combine owned products with plan/pass-entitled titles, and include an indicator of what can be read here. No output schema exists, so this return-content framing is genuinely useful; only ordering/pagination and progress info remain undisclosed.

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?

Single compact sentence with no wasted clauses, which is good. But the leading fragment "Members." is ambiguous and does not front-load the action, and brand jargon ("Niche of One products") is used without clarification, slightly blunting the opening.

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

Completeness4/5

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

For a zero-parameter read tool with full annotation coverage and no output schema, the description supplies the two things an agent most needs: who the results are scoped to and what categories of items come back. Only minor gaps remain, such as whether reading status or progress is included and whether results are ordered or paginated.

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

Parameters4/5

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

The tool takes no parameters and the schema is fully described, so there is no parameter meaning for the description to add. Baseline applies.

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 uses a clear verb ("List") with a specific resource: Niche of One products owned by the signed-in member, plus plan/pass-included titles and readability status. That is materially more precise than the name alone. It does not, however, distinguish itself from sibling tools with similar names such as read_library or reader_library, leaving the agent to guess which library view applies.

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?

Usage is only implied by the phrase "this signed-in member owns"; there is no explicit statement of when to call this instead of read_library, reader_library, or my_account. No exclusions, prerequisites, or alternative-routing guidance are provided, so the agent must infer selection from the tool name.

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