Skip to main content
Glama

Quote Of The Day

quote_of_the_day
Read-onlyIdempotent

Daily featured quote (English Wikiquote, lang=fr returns its locale equivalent where available).

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": {
      "lang": "en"
    },
    "name": "quote_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo

Output Schema

NameRequiredDescriptionDefault
parseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that `lang=fr` resolves to the French Wikiquote equivalent 'where available', hinting at fallback behavior, but leaves the fallback rule and default language unstated.

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?

A single compact sentence with the source and the notable parameter behavior front-loaded. Nothing is wasted, though the parenthetical phrasing makes the fallback semantics slightly cryptic.

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?

An output schema exists, so return values need no explanation, and the tool is inherently simple. Still, the vague 'where available' clause and the unstated default for omitted `lang` leave an agent guessing about behavior for non-English locales.

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 0% and the schema only declares `lang` as a bare string, so the description carries the burden. It explains what `lang=fr` does and implies an English default, but says nothing about unsupported locale values or what happens when a locale edition is missing.

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?

States a concrete resource ('Daily featured quote') plus its source ('English Wikiquote'), which goes beyond the tautological title. No sibling overlaps with this function, so differentiation is not a concern.

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: fetch today's featured quote. There is no explicit when-to-use or when-not guidance, though the tool's single, narrow purpose makes alternatives largely irrelevant.

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.