Skip to main content
Glama

Wikiquote Search

wikiquote_search
Read-onlyIdempotent

Wikiquote title + fulltext search.

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

Input Schema

NameRequiredDescriptionDefault
langNo
limitNo1-50 (default 10)
queryYes

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesWikiquote search results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / items / items / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "array"
      +]
  2. Added

TDQS

B3/5.0
Behavior3/5

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

The description provides minimal behavioral information, but since a wealth of behavioral constraints (idempotency, read-only status, etc.) are provided in the annotations, the description adds some useful context despite its brevity.

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 definition is extremely short and highly focused, dedicating every word to defining the core functionality and search types of the tool.

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?

Given the low parameter coverage and the complex nature of scoped searches (language, limits), the description is too brief to provide adequate guidance on how an agent should construct a helpful query.

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?

With only 33% schema coverage, the description fails to compensate for the missing semantic detail in the input schema. It does not elaborate on how the `lang` or `limit` parameters are intended to be used in a meaningful way beyond being search qualifiers.

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?

The description clearly defines the search capability by specifying both 'title' and 'fulltext' search capabilities within Wikiquotes, which provides necessary scope for a search tool.

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?

The description offers no guidance on when this specific tool should be used versus other available search alternatives. It is a simple declarative statement of function with no usage context.

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.