Skip to main content
Glama

Unified Reading

Unified Reading options

get_unified_reading_options
Read-only

List what Unified Reading offers (free sample, free preview, paid full reading), its price, and the pages a person should open. Collects no personal data.

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

Input Schema

NameRequiredDescriptionDefault
optionNoReturn only one option, or all of them.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / option / enum
      Previous value: -[
      -  "all",
      -  "sample",
      -  "preview",
      -  "fullReading"
      -]New value: +[
      +  "all",
      +  "sample",
      +  "preview",
      +  "fullReading",
      +  "couplesReading"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds a genuine behavioral fact beyond that: "Collects no personal data," which reassures an agent that no PII is gathered. However, it says nothing about the shape or size of the response, pagination, or price currency, so the added value is limited.

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 short sentences with no filler, and the core content is front-loaded before the privacy note. The phrase "the pages a person should open" is slightly vague about what those pages are, a minor clarity cost in an otherwise tight definition.

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-required-parameter, single-enum read tool with no output schema, the description covers the essentials: what is returned, that it is free of personal-data collection, and which option values exist. It does not describe the return structure or price formatting, but nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100% and the single enum parameter is fully documented in the schema, so the baseline is 3. The description goes slightly beyond by naming three of the option values (sample, preview, full reading), reinforcing what each selection yields, though it does not explain the couplesReading option or the default behavior.

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 specific verb ("List") and a specific resource ("what Unified Reading offers") and enumerates the returned content: free sample, free preview, paid full reading, price, and the pages to open. This clearly separates it from the unrelated siblings (zodiac year, birth date profile), though it does not explicitly name an alternative.

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?

Usage is only implied: an agent can infer it should call this to discover reading offerings and pricing. There is no explicit statement of when to use it versus when not, nor any prerequisites or exclusions, and the sibling tools are in different domains so no routing guidance is provided.

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.