Skip to main content
Glama

CIPHER x402 — Paid Solana & Crypto Tools

by io.github.cryptomotifs

pubmed_medical_search

Search PubMed (NCBI) for medical / life-sciences literature by keyword. Returns enriched article list: pmid, title, authors, journal, year, pub_types, plus a year-range + has-meta-analysis / has-review enrichment block. Ideal for medical RAG agents. Priced at $0.005 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesFree-text biomedical query (e.g. 'metformin liver', 'semaglutide cardiovascular outcomes').
retmaxNoMax articles to return (1-20). Default 5.
_paymentNoOptional. Signed x402 v2 X-PAYMENT header value (base64-encoded EIP-3009 authorization). If present, forwarded upstream; if absent, tool returns the 402 accept-list.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description fully discloses the payment mechanism (pricing, required authorization for paid response, and the fallback behavior returning a 402 accept-list). It also describes the enriched output structure. No other behavioral traits (e.g., rate limits) are mentioned, but the key behavioral aspect (payment) is well-covered.

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?

The description is concise with five sentences, each adding value: purpose, output, use case, pricing, and payment behavior. Front-loaded with the main action. No redundancy.

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?

Given the tool's complexity (payment, no output schema), the description covers the core functionality, output fields, and payment workflow. Missing details like error handling or empty response, but these are minor for a search tool. Overall adequate.

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 coverage is 100%, so baseline is 3. The description adds value by describing the return format (list of fields, enrichment block) which is not in the input schema. It also clarifies the purpose of the '_payment' parameter beyond the schema description. This extra context elevates the score.

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?

The description clearly states the tool searches PubMed for medical/life-sciences literature, a specific verb and resource. It also mentions the enriched output, making the purpose unambiguous. No similar sibling tools exist, so differentiation is not needed.

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?

The description identifies the tool as 'Ideal for medical RAG agents,' providing a clear use case. However, it does not explicitly state when not to use it or mention alternatives, though sibling tools are unrelated.

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

All CIPHER x402 — Paid Solana & Crypto Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose with detailed descriptions, and there is no functional overlap between any tools, even those in similar domains like geocoding (forward vs reverse) or Solana wallet analysis (general scan vs specific protocol exposure).

Naming Consistency2/5

Tool names follow no consistent pattern: some use verb_noun (check_drift_exposure), others use data source prefix (coinalyze_funding_rates, openfda_adverse_events), and a few use domain prefix (solana_wallet_scan). This mixture of conventions makes it hard to predict naming for similar functions.

Tool Count2/5

The server claims to be for Solana & Crypto but only 6 of 15 tools are crypto-related, while the rest cover unrelated domains like medical, nutrition, and geocoding. This dilutes focus and suggests the tool count is mismatched for the stated purpose.

Completeness2/5

For a server named 'Paid Solana & Crypto Tools', the crypto toolset is incomplete, missing common operations like token swaps, DeFi protocol interactions, or NFT queries. The inclusion of many non-crypto tools does not fill these gaps.

Resources