Skip to main content
Glama

Get a topic research pack (paid)

get_research_pack
Read-onlyIdempotent

PAID per call via x402. Topic research pack: the topic dossier plus the 50 most influential and 25 newest papers (licensed abstracts included) and related clinical trials. Price: $0.20 (USDC on Base, x402).

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": {
      "topic": "<topic>"
    },
    "name": "get_research_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), and the description adds billing behavior the annotations cannot express: per-call payment via x402, the exact price and currency/chain. It stops short of explaining how payment is actually satisfied (402 challenge, retry, wallet requirements) or whether a free preview exists via preview_dossier.

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?

Two dense sentences with no filler, and the payment warning is correctly front-loaded before the contents. Minor waste from stating "x402" twice in the same short description.

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?

With no output schema, the description carries the full burden of describing the return value; it does enumerate the contents well but not the response shape (sections, pagination, whether full text or abstracts only beyond the licensed abstracts note). For a paid, non-idempotent-in-practice operation, the missing payment flow explanation is a real gap.

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?

There is only one parameter and the schema already documents it at 100% coverage ("Topic slug"), so the baseline of 3 applies. The description implies that the topic drives the whole pack, but does not say whether the slug must come from list_topics or what happens on an unknown slug.

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?

Uses a specific verb and resource ("Topic research pack") and enumerates exactly what the pack contains: the topic dossier, the 50 most influential and 25 newest papers with licensed abstracts, and related clinical trials. This clearly distinguishes it from siblings like get_dossier, get_paper, and get_topic, which return single artifacts, so an agent can pick it 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 Guidelines4/5

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

States the cost model up front ("PAID per call via x402", "$0.20 USDC on Base"), which is a decisive selection signal against the free single-artifact siblings. However, it never names an alternative or states when NOT to use it, e.g. that get_paper or get_dossier should be used when only one artifact is needed.

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