Skip to main content
Glama

Wikiquote Summary

wikiquote_summary
Read-onlyIdempotent

Page summary.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
titleYes

Output Schema

NameRequiredDescriptionDefault
dirNoText direction (ltr/rtl)
langNoLanguage code
titleNoPage title
extractNoPage summary text
revisionNoRevision ID
thumbnailNo
displaytitleNoDisplay title
lastmodifiedNoLast modification date
originalimageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on language fallback behavior, whether a missing page errors or returns empty, or what the open-world lookup implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words contain no waste but also no content; this is under-specification rather than conciseness. There is no front-loaded statement of action or scope that an agent could act on.

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

Completeness1/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 described, and annotations cover safety. Even granting that relief, a two-word fragment for a 2-parameter tool with 0% schema coverage leaves the language parameter and error behavior completely undocumented, making the definition inadequate.

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 description coverage is 0%, so the description carries the full burden and fails it: neither "title" nor "lang" is explained. Only the word "page" loosely implies a page identifier; the format of the language code (e.g. "de") and whether it is optional are left entirely to inference.

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

Purpose2/5

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

"Page summary." restates the tool name (Wikiquote Summary) rather than stating a verb and resource, so it is essentially tautological. An agent can guess it returns a summary of a Wikiquote page, but nothing distinguishes it from wikiquote_quotes or wikiquote_search or explains what a "summary" contains.

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 when-to-use guidance, no mention of alternatives such as wikiquote_search or wikiquote_quotes, and no stated preconditions. The agent must infer that this is the right tool when a condensed page overview is wanted rather than quotes or search results.

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.