Skip to main content
Glama

raras

by io.github.rarasAI
OverviewDiscussionsAdmin

Buscar fenótipos HPO

search_phenotypes
Read-only

Lookup HPO em PT-BR (encoder Araras-HPO-Brasil + léxico leigo) ou EN (vocabulário HPO). Retorna IDs HP: com estado de asserção: termo NEGADO ("nunca desmaiei") NÃO vira fenótipo. Outros idiomas não são cobertos. Limite de taxa: use poucas chamadas por minuto (429 = espere).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
noteNo
queryYes
resultsYes
assertionYes
languagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "assertion": {
+      "enum": [
+        "PRESENT",
+        "NEGATED"
+      ],
+      "type": "string"
+    },
+    "languages": {
+      "type": "string"
+    },
+    "meta": {},
+    "note": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "hpoId": {
+            "type": "string"
+          },
+          "match": {
+            "enum": [
+              "exact",
+              "approximate"
+            ],
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "namePt": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "similarity": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "via": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "hpoId",
+          "name",
+          "namePt",
+          "match",
+          "via",
+          "similarity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "assertion",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral detail: negated expressions like 'nunca desmaiei' must not be converted into phenotypes, only PT-BR and EN are supported, and HTTP 429 means wait. This is exactly the kind of non-obvious behavior an agent needs to know and is not available from annotations alone.

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 short sentences deliver all critical information without redundancy. The main lookup purpose and language scope come first, followed by the negation caveat and rate-limit guidance. Every sentence earns its place.

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?

For a two-parameter lookup tool with a readOnlyHint and an output schema, the description is complete. It covers language coverage, negation behavior, return type, and operational constraints. The presence of an output schema means the return shape does not need to be repeated in prose.

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 0%, so the description must compensate. It does clarify the meaning of the query parameter by specifying supported languages and the negation rule. The limit parameter is left to the schema, but its name, type, default, minimum, and maximum are self-explanatory, so the overall parameter semantics are adequately covered.

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 states a specific verb ('Lookup'), a specific resource (HPO terminology), and the supported languages (PT-BR and EN). It also states the output type (HP IDs) and a key domain rule (negated terms do not become phenotypes), making the tool's purpose unmistakable and distinct from general disease or paper searches.

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 gives useful context: only PT-BR and EN are covered, and rate limits require few calls per minute. However, it does not explicitly compare this tool to sibling tools or state when an alternative like analyze_clinical_case or find_phenotypically_similar should be used instead. Usage is implied rather than explicitly delineated.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources