Skip to main content
Glama

mosaic_drug_repurposing

Read-onlyIdempotent

Identifies new therapeutic indications for a compound based on its target's disease associations, highlighting opportunities where the compound is not yet clinically tested.

Instructions

Find new indications where a compound's primary targets are implicated.

Returns indications where the compound's targets have supporting evidence but the compound itself is not yet clinically active. Ranked by a simple target-support × avg-evidence score. Useful as a starting point for repurposing hypotheses — not a substitute for clinical review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds value by explaining the ranking mechanism and that results are not a clinical substitute. No contradictions.

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?

Two sentences, no filler. Each sentence adds value. Front-loaded with primary purpose.

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 output schema exists, explanation of return values is not needed. Description covers use case and scoring. Missing limit parameter behavior is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. The description implies compound_name as input but does not describe it or the limit parameter. Missing parameter details for a low-coverage scenario.

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's purpose: 'Find new indications where a compound's primary targets are implicated.' It specifies the output logic and contrasts with clinical review, distinguishing it from sibling tools like mosaic_find_opportunities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Description mentions it's 'useful as a starting point for repurposing hypotheses — not a substitute for clinical review,' providing some guidance but lacks explicit when-not-to-use or naming of alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sourabhnk/mosaic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server