Skip to main content
Glama
Sign In
web-explorer

web-explorer

by cutlerbenjamin1-cmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wiki

Search and retrieve encyclopedia articles with query or title. Results are cached for one hour.

Instructions

Wikipedia lookup. Check memory/KG for known facts first. Actions: search, page. Results cached 1hr.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
titleNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, description carries full burden. Discloses caching behavior ('Results cached 1hr.') and enumerates actions. No contradictions; clearly a read-only lookup.

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?

Two concise sentences with front-loaded purpose. Every sentence adds value: purpose, usage guideline, actions, caching. No unnecessary words.

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?

Describes purpose, usage, actions, and caching. However, lacks explanation of parameter distinctions and return value (no output schema). Leaves gaps for an agent to understand fully.

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%, so description must compensate. It lists actions (search, page) which maps to action enum, but does not clarify when to use 'query' vs 'title' parameters. Partial help, but significant ambiguity remains.

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?

Clearly states 'Wikipedia lookup' which is a specific verb+resource. Distinguishes from siblings like wikidata_query and web search. Mentions two actions (search, page), adding clarity.

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

Usage Guidelines4/5

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

Instructs to check memory/KG first, indicating proper usage order. Does not explicitly name alternatives or when not to use, but provides context for effective use.

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

Deploy Server

Other Tools