Skip to main content
Glama

Research search

research_search

Research search: Wikipedia, Wikidata, Wikivoyage travel guides, Wiktionary (meanings, translations), PsychonautWiki harm reduction (dose, duration, dangerous combinations), Open Targets drugs and diseases, arXiv, OpenAlex scholarly works, Hacker News and Stack Overflow in one call, about a second, each hit with its source, link, excerpt and date. Pass q; optional sources and limit. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "q": "<q>"
    },
    "name": "research_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYeswhat to search for, 2-200 characters
limitNoresults per source, 1-10 (default 5)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
sourcesNocomma list to ask: wikipedia, wikidata, wikivoyage, wiktionary, psychonautwiki, opentargets, chembl, arxiv, openalex, hackernews, stackoverflow (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "results per source, 1-10 (default 5)",
      +  "type": "string"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "what to search for, 2-200 characters",
      +  "type": "string"
      +}
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "comma list to ask: wikipedia, wikidata, wikivoyage, wiktionary, psychonautwiki, opentargets, chembl, arxiv, openalex, hackernews, stackoverflow (default all)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "q"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and largely meets it: it discloses price ($0.003 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), latency (~1 second), and the exact two-step x402 signing flow including that the purchase completes inside the call when payment is supplied. It omits failure behavior, partial-source failures, and any rate limits or refund semantics for a paid endpoint.

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

Conciseness4/5

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

Front-loads the value proposition (all sources in one call, ~1s) before cost and payment mechanics, and every clause is informative. The source enumeration is long but serves selection; the flow is a single dense paragraph rather than clearly separated sections.

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?

For a 4-parameter paid search tool with no output schema, it covers coverage, cost, payment protocol, return fields and latency — enough to call it correctly first try. Missing only edge-case behavior (what happens on an expired or rejected payment, behavior when a source returns nothing).

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 100%, so the schema already defines q, limit, sources and payment. The description restates q/sources/limit without adding format detail and adds only modest meaning for `payment` by describing the sign-then-resubmit loop. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb (search) and enumerates the concrete corpora covered (Wikipedia, Wikidata, Wikivoyage, Wiktionary, PsychonautWiki, Open Targets, arXiv, OpenAlex, Hacker News, Stack Overflow), so an agent knows exactly what data this reaches. States the return shape (source, link, excerpt, date) and latency, which further distinguishes it from sibling tools.

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?

Gives clear operational context: pass q, optionally narrow with sources and limit, and follow a two-call payment flow (call without payment for terms, sign, call again). It does not name alternatives such as web_read, market_search, or find_open_datasets, so when-not-to-use is left to inference.

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.

Resources