Skip to main content
Glama

Zenquotes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Today Quote

today_quote
Read-onlyIdempotent

Get the quote of the day from ZenQuotes. Returns the same quote for all requests within a given day.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
quoteYesThe quote of the day text
authorYesThe author of the quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "The author of the quote",
+      "type": "string"
+    },
+    "quote": {
+      "description": "The quote of the day text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "quote",
+    "author"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already indicate read-only and idempotent, but the description adds the temporal detail that the quote is constant across requests within a day and names the external source, which are useful behavioral insights not captured by the annotations.

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?

The description is two sentences, each carrying essential information: the action and the key behavioral trait. No redundancy.

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?

This is a simple, parameter-free tool with an output schema; the description adequately covers what it does and its main behavioral characteristic, leaving nothing essential unexplained.

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, so the description does not need to explain parameter semantics. The schema already covers everything, earning the baseline score of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Get') and a distinct resource ('the quote of the day from ZenQuotes'), and it differentiates from siblings by noting the consistency within a day.

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

Usage Guidelines4/5

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

The description implies the primary use case—retrieving a deterministic daily quote—and the 'same quote for all requests within a given day' provides clear context for when this tool is appropriate, though it does not explicitly contrast with alternatives like random_quote.

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

All Zenquotes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources