Skip to main content
Glama

Opentargets

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds useful behavioral detail about scoping to an identifier (anonymous IP, BYO key hash, or account ID) and the optional listing behavior. This goes beyond what annotations provide.

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, front-loaded with the core action. Each sentence adds necessary context: behavior, use case, and scoping. No filler.

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 simple tool with one optional parameter and no output schema, the description covers the retrieval action, the listing mode, scoping, and integration with sibling tools (remember, forget). It is sufficiently complete for an agent to select and invoke it correctly.

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%, with the 'key' property already described as 'Memory key to retrieve (omit to list all keys)'. The description reinforces this by explicitly noting the omission behavior and giving examples of typical values, but adds no new semantic information beyond the schema.

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 defines the tool's action ('Retrieve a value' or 'list all saved keys') and resource ('previously saved via remember'). It distinguishes from siblings by referencing 'remember' and 'forget' and giving concrete use cases (ticker, address, research notes).

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?

Explicitly states when to use: when the agent needs context saved earlier, without re-deriving it. It also instructs how to list all keys (omit the key argument) and mentions pairing with remember (save) and forget (delete). This provides clear usage context and lifecycle guidance.

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

All Opentargets 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
Disambiguation2/5

Several clusters of tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions; entity_profile, compare_entities, and recent_changes all pull company data; polymarket_edges, polymarket_arbitrage, and bet_research all analyze prediction markets. Though descriptions are detailed, the boundaries are subtle and the beta variant is nearly identical to the stable one.

Naming Consistency3/5

Most names are snake_case, but there's no consistent verb_noun pattern: some are bare nouns (disease, target, drug, search), some are verb phrases (resolve_entity, validate_claim, generate_llms_txt), and some are domain-prefixed (ask_pipeworx_*, polymarket_*, target_*). The mixed conventions make it hard to predict tool names.

Tool Count2/5

38 tools is far beyond the typical well-scoped server, and the set mixes Open Targets lookup, a general data platform (Pipeworx), prediction markets, npm package checks, and AI-marketing utilities under the name 'Opentargets'. Many tools are unrelated to the server's apparent core purpose.

Completeness4/5

The Open Targets drug-discovery workflow is well covered: search for IDs, get disease/drug/target profiles, and get associations/known drugs. However, the broader platform lacks some lifecycle operations (no create/update/delete since it's read-only), and the unrelated utilities (generate_llms_txt, scan_dependency) appear tacked on rather than filling domain gaps.

Resources