Skip to main content
Glama

Wikiquote Quotes

wikiquote_quotes
Read-onlyIdempotent

Extract sourced quotation items from a page.

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": {
      "title": "Albert Einstein"
    },
    "name": "wikiquote_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
limitNoMax quotes returned (default 50)
titleYes

Output Schema

NameRequiredDescriptionDefault
langYesLanguage code
countYesNumber of quotes extracted
titleYesPage title
quotesYesArray of extracted quotes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 contributes one genuinely useful behavioral qualifier — "sourced", implying returned quotes carry citations/attributions — but says nothing about failure behavior for missing titles, language fallback, or result ordering.

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?

A single front-loaded sentence with no filler, which is structurally clean. The problem is under-specification rather than verbosity: for a three-parameter tool it spends too few words to be actionable.

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

Completeness2/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 explained. However, with a required page identifier and an undocumented `lang` selector, the definition leaves the agent guessing on inputs and gives no routing guidance among the wikiquote siblings — not enough for the tool's modest but real complexity.

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

Parameters2/5

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

Schema coverage is only 33%: `limit` is documented but `lang` and the required `title` are not. The description's phrase "from a page" only loosely gestures at `title` and never explains `lang` (language edition selection) or its default, so it does not compensate for the coverage gap.

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

Purpose3/5

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

"Extract sourced quotation items" gives a verb and a resource, and the word "sourced" distinguishes it from a bare quote generator like quote_of_the_day. But "from a page" is ambiguous — the required parameter is actually a `title`, so an agent cannot tell whether it needs a URL, a page title, or a search string, and nothing separates it from wikiquote_search.

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?

There is no statement of when to use this rather than wikiquote_search (find a page) or quote_of_the_day (random quote). No prerequisites, no note on what happens when the title does not exist, and no exclusions are given.

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.