Skip to main content
Glama

Clinicaltrials

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds scoping and pairing details, enhancing transparency beyond annotations.

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?

Three sentences, each carrying distinct information. Front-loaded with the primary action. No wasted words.

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?

Given only one optional parameter and no output schema, the description covers retrieval behavior, listing mode, use cases, scoping, and paired tools. Complete for the tool's complexity.

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%. Description restates the key parameter's usage but adds no new format or constraint details beyond the schema. Adequate but not enriched.

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?

Description uses a specific verb ('retrieve') and resource ('value previously saved via remember'), and clearly distinguishes from sibling tools like 'remember' and 'forget' by stating the pairing.

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?

Explicitly states when to use ('to look up context') and the scoping mechanism. Could mention when not to use, but the description is clear enough for an agent.

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

All Clinicaltrials 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.9/5.0
Disambiguation3/5

Tool families overlap in purpose—ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded, ct_search/ct_count_by_condition/ct_competitive_landscape, and ct_sponsor_trials/ct_sponsor_pipeline/ct_sponsor_activity all present multiple plausible entry points. The very detailed, cross-referenced descriptions help, but an agent still has to read carefully to avoid misselection.

Naming Consistency4/5

Nearly all tool names follow lowercase snake_case with recognizable prefixes like ct_, polymarket_, and pipeworx_, giving the set a strong overall pattern. The main deviation is noun-phrase names such as recent_changes, entity_profile, and pipeworx_trending instead of a more uniform verb-first convention.

Tool Count2/5

44 tools is far too many for a server named Clinicaltrials: only 13 are ct_* tools, while the other 31 are broad Pipeworx utilities covering prediction markets, memory, subscriptions, npm scanning, and AI visibility. The clinical-trial module itself is well-sized, but the server bundles substantial unrelated surface area.

Completeness4/5

The clinical-trial workflow is nearly complete: search, study details, results, counts, sponsor comparison and pipeline, location lookup, update tracking, and landscape mapping are all covered. Minor conveniences like saved searches or export are missing, but agents can work around them; there are no dead ends in the registry domain.

Resources