Estatísticas do grafo
get_graph_statsContagens e métricas do dataset.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
raras
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states 'counts and metrics' without mentioning return format, side effects, performance, or other behavioral traits. It implies a read-only operation but does not explicitly confirm this.
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?
The description is a single, concise phrase that is immediately understandable. It is front-loaded with the key information with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters, but the description does not specify which metrics are included or what 'dataset' refers to in the graph context. It is minimally sufficient but leaves ambiguity about the exact content of the statistics.
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?
The tool has zero parameters, so parameter semantics are trivially satisfied. The description need not add parameter details, and the baseline for 0-parameter tools is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Contagens e métricas do dataset' clearly indicates the tool provides counts and metrics for the dataset, which is a specific output. However, it lacks an explicit verb and does not differentiate from sibling tools beyond the name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus the many sibling tools. The description does not mention any context, constraints, or alternatives, leaving the agent without direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.