Skip to main content
Glama

raras

by io.github.rarasAI

Hipóteses de reposicionamento (co-scientist)

get_hypotheses
Read-only

Candidatos a reposicionamento de fármacos gerados por associação de genes (guilt-by-association): drogas que tratam outras doenças que compartilham genes com esta. HIPÓTESES para investigação, NUNCA recomendações clínicas — cada uma rastreável (via gene X, da doença Y).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orphaCodeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
methodYes
orphaCodeYes
hypothesesYes
isRecommendationYes

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that results are generated via guilt-by-association, are hypotheses only, and are traceable via gene and disease. This adds meaningful behavioral context without contradicting the annotations.

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?

The description is a single, dense sentence that efficiently conveys purpose, method, and caveat. It avoids unnecessary fluff while packing essential information.

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 read-only, single-parameter tool with an existing output schema, the description provides strong contextual completeness: it explains what the tool does, how results are generated, and the crucial caveat that they are hypotheses. The only minor gap is the implicit parameter definition.

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?

The input schema has zero description coverage, but the description implies the 'orphaCode' parameter refers to the disease in question via 'compartilham genes com esta.' This is not explicit, so the parameter semantics are only partially addressed.

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 returns drug repositioning candidates generated by gene association (guilt-by-association), and explicitly distinguishes these as hypotheses, not clinical recommendations. This specificity differentiates it from sibling tools like get_evidence or find_similar_diseases.

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?

The description implies the tool is for investigating drug repositioning hypotheses and includes a strong warning that results are never clinical recommendations. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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

All raras 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

B3/5.0
Disambiguation4/5

Most tools have clear, distinct purposes, but there is a cluster of 'find' tools (find_similar_diseases, find_phenotypically_similar, find_diseases_by_phenotypes) that could be confused; descriptions differentiate them (semantic vs HPO similarity vs exact match), and the paper search tools also differ by input type. Overall, ambiguous pairs are explicitly disambiguated, leaving only a few close calls.

Naming Consistency5/5

All tools consistently follow a snake_case verb_noun pattern, using a limited set of verbs (analyze, explain, find, get, search) that map predictably to tool functionality. No mixed conventions or vague names are present, making the naming highly systematic.

Tool Count4/5

At 20 tools, the server is slightly above the ideal range of 3-15, but each tool serves a distinct function within the rare disease knowledge platform. The breadth of features—search, similarity, detail, evidence, literature, hypotheses, graph exploration—justifies the count without feeling bloated or redundant.

Completeness5/5

The tool surface comprehensively covers the rare disease domain: search, differential diagnosis, disease detail, evidence, SUS/trials, reference centers, literature, hypotheses, and graph analytics. Write operations are not expected for a read-only knowledge base, and the inclusion of research log and recent updates closes all apparent gaps.

Resources