Skip to main content
Glama

ZenQuotes (Unofficial)

Zenquotes Random Quote

zenquotes_random_quote
Read-onlyIdempotent

Fetch a single random inspirational quote (author + text) from ZenQuotes; falls back to dummyjson automatically if ZenQuotes is unavailable. Response includes _source field when served from fallback.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
quoteYesThe inspirational quote text
authorYesThe author of the quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior beyond them: the automatic fallback to dummyjson when ZenQuotes is unavailable, and the _source marker in the response that signals fallback provenance — both operationally important for interpreting results.

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?

Two short clauses, front-loaded with the primary action and resource, then the fallback caveat. Every phrase carries information — what is returned, from where, and what happens on failure — with no filler.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out, and the description still flags the one non-obvious output detail (_source on fallback). For a zero-parameter read tool with full annotation coverage, nothing an agent needs to call 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly spends no space on inputs and instead uses it for output provenance.

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?

Specific verb and resource: 'Fetch a single random inspirational quote (author + text) from ZenQuotes'. The words 'single' and 'random' implicitly separate it from list_quotes and today_quote, but no sibling is named, so the agent must infer the distinction from name similarity alone.

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 word 'random' hints at the use case (a spontaneous quote rather than a curated list or today's quote), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is implied rather than stated.

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.