Skip to main content
Glama

Wikipedia Lookup

wikipedia_lookup
Read-onlyIdempotent

Look up topics on Wikipedia and receive concise summaries with page URLs. Ideal for encyclopedic facts about people, places, concepts.

Instructions

Look up a topic on Wikipedia and return a concise summary (with the page URL). Prefer this over web_search for encyclopedic facts about people, places, concepts and events.

Args:

  • query (string): The topic or article title to look up.

  • lang (string): Wikipedia language code (default 'en').

Returns { title, summary, url }.

Example: { "query": "Alan Turing" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesTopic or article title
langNoLanguage codeen
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. Description adds return format (title, summary, url) and default language, providing useful context beyond 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?

Concise, includes example and return structure. No filler words.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, parameters, return, and example. Lacks details on error handling or summary length, but acceptable for a simple lookup tool.

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?

Schema covers both parameters with descriptions. Description adds an example and default value for lang, slightly enhancing clarity.

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?

Description clearly states it looks up a topic on Wikipedia and returns a concise summary with URL. It also distinguishes itself from web_search for encyclopedic facts.

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

Usage Guidelines5/5

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

Explicitly advises to prefer this tool over web_search for encyclopedic facts, providing clear guidance on when to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/highercomve/mcptools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server