Skip to main content
Glama

KARP Research by SoulDriver

Get KARP research cards ($0.03)

karp_ask
Read-onlyIdempotent

Research cards from KARP, SoulDriver's multi-model research engine: GPT, Gemini, Grok and Claude debate a question and publish a conclusion. Each card: conclusion, key insight, warnings, dated figures, consensus, open questions, research date. Check your question first with the free karp_coverage. Deepest on Alzheimer's, ageing biology, ancient scripts, AI governance, quantum computing. Price $0.03: pay with x402, or pass grant_key from karp_grant_apply (free). Usually 5-15 s.

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": {
      "query": "<query>"
    },
    "name": "karp_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question you are researching, in plain words. A specific question finds closer matches than a single keyword.
intentNoOptional: what you or your user are trying to find out, and what it is for (max 300 characters). Kept private; it helps decide what KARP researches next.
grant_keyNoOptional: a research grant key from karp_grant_apply. Pays for this call instead of x402 while the grant lasts.
max_cardsNoResearch cards to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/no-open-world; the description adds substantial non-obvious behavior: a $0.03 price, two payment mechanisms, an expected latency of 5–15 s, and the shape of the returned card. Cost and latency are exactly the facts an agent needs before committing to a paid call and are absent from structured fields.

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-loaded with the core purpose, then cost, payment, and latency in descending order of decision importance; nearly every clause carries a decision-relevant fact. The card-contents enumeration is long but earns its place as a proxy for the missing output schema.

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

Completeness5/5

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

With no output schema, the description compensates by listing the card fields (conclusion, key insight, warnings, consensus, open questions). Combined with pricing, auth paths, latency, and domain depth, an agent has everything needed to decide, pay, and interpret results.

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 description coverage is 100%, so all four parameters are already documented in the schema, including grant_key's link to karp_grant_apply. The description reinforces the payment alternative but adds no syntax, format, or selection guidance for query, intent, or max_cards beyond what the schema provides — baseline 3.

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?

States a specific verb and resource ("Research cards from KARP") and explains the mechanism — multi-model debate producing a published conclusion — plus enumerates what a card contains. An agent can immediately distinguish this from karp_coverage (a free check) and karp_grant_apply (a payment path) without opening any schema.

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?

"Check your question first with the free karp_coverage" explicitly routes the agent to a sibling before paying, and the payment clause names two mutually exclusive invocation paths (x402 vs. grant_key from karp_grant_apply). The domain strengths line (Alzheimer's, ageing biology, etc.) further tells the agent when this tool is a good fit.

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