Query the MetaDome server to discover supported features, detail levels, and response modes before making requests.
Signature: get_server_capabilities(detail=, response_mode=).
| Name | Required | Description | Default |
|---|---|---|---|
| detail | No | Detail level. | |
| response_mode | No | Mode. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.7Input schema / properties / detail / defaultRemoved value: -"summary"Input schema / properties / detail / descriptionPrevious value: -"summary (default, light) or full (adds semantics + notes)."New value: +"Detail level."Input schema / properties / detail / typeRemoved value: -"string"Input schema / properties / response_mode / defaultRemoved value: -"compact"Input schema / properties / response_mode / descriptionPrevious value: -"Verbosity: minimal|compact|standard|full (default compact)."New value: +"Mode."Input schema / properties / response_mode / typeRemoved value: -"string"Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "M": {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(tool|request_id|capabilities_version)$": {
+ "type": "string"
+ },
+ "^data_versions$": {
+ "$ref": "#/$defs/V"
+ },
+ "^elapsed_ms$": {
+ "type": "integer"
+ },
+ "^next_commands$": {
+ "items": {
+ "additionalProperties": false,
+ "minProperties": 2,
+ "properties": {
+ "arguments": {
+ "propertyNames": {
+ "const": "query"
+ },
+ "type": "object"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "^unsafe_for_clinical_use$": {
+ "const": true
+ }
+ },
+ "required": [
+ "tool",
+ "request_id",
+ "data_versions",
+ "unsafe_for_clinical_use"
+ ],
+ "type": "object"
+ },
+ "V": {
+ "additionalProperties": false,
+ "minProperties": 8,
+ "patternProperties": {
+ "^(assembly|gencode|uniprot|gnomad|clinvar|pfam|metadome_app|data_doi)$": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "oneOf": [
+ {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(dropped_summary|server|server_version|capabilities_version|data_source|data_version|genome_build|data_currency_caveat|research_use_notice|recommended_citation|license|default_response_mode|detail|more|async_model|score_semantics|provenance_policy|per_call_meta_semantics)$": {
+ "type": "string"
+ },
+ "^(read_only|research_use_only)$": {
+ "type": "boolean"
+ },
+ "^(tools|response_modes|error_codes|recommended_workflows|per_call_meta)$": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "^_meta$": {
+ "$ref": "#/$defs/M"
+ },
+ "^build$": {
+ "additionalProperties": false,
+ "minProperties": 3,
+ "patternProperties": {
+ "^(version|git_sha)$": {
+ "type": "string"
+ },
+ "^built_at$": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "^data_versions$": {
+ "$ref": "#/$defs/V"
+ },
+ "^limits$": {
+ "additionalProperties": false,
+ "minProperties": 3,
+ "patternProperties": {
+ "^(max_batch_positions|default_page_limit|max_page_limit)$": {
+ "type": "integer"
+ }
+ },
+ "type": "object"
+ },
+ "^success$": {
+ "const": true
+ },
+ "^tool_count$": {
+ "type": "integer"
+ },
+ "^tool_modes$": {
+ "additionalProperties": false,
+ "minProperties": 2,
+ "patternProperties": {
+ "^(read_only|compute_orchestration)$": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "success",
+ "_meta",
+ "server",
+ "server_version",
+ "build",
+ "capabilities_version",
+ "data_versions",
+ "tools",
+ "tool_count",
+ "response_modes",
+ "error_codes",
+ "read_only",
+ "tool_modes",
+ "research_use_only",
+ "data_source",
+ "data_version",
+ "genome_build",
+ "recommended_citation",
+ "license",
+ "limits",
+ "default_response_mode",
+ "detail"
+ ]
+ },
+ {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(message|recovery_action|field|hint)$": {
+ "type": "string"
+ },
+ "^_meta$": {
+ "$ref": "#/$defs/M"
+ },
+ "^allowed_values$": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "^error_code$": {
+ "enum": [
+ "invalid_input",
+ "not_found",
+ "ambiguous_query",
+ "upstream_unavailable",
+ "rate_limited",
+ "internal"
+ ]
+ },
+ "^retryable$": {
+ "type": "boolean"
+ },
+ "^success$": {
+ "const": false
+ }
+ },
+ "required": [
+ "success",
+ "_meta",
+ "error_code",
+ "message",
+ "retryable",
+ "recovery_action"
+ ]
+ }
+ ],
+ "type": "object"
+}v0.3.1Output schema / (root)Previous value: -{
- "additionalProperties": true,
- "properties": {
- "_meta": {
- "additionalProperties": true,
- "type": "object"
- },
- "candidates": {
- "type": "array"
- },
- "capabilities_version": {
- "type": "string"
- },
- "data_versions": {
- "additionalProperties": true,
- "type": "object"
- },
- "error_code": {
- "type": "string"
- },
- "error_codes": {
- "type": "array"
- },
- "field": {
- "type": "string"
- },
- "hint": {
- "type": "string"
- },
- "message": {
- "type": "string"
- },
- "read_only": {
- "type": "boolean"
- },
- "recommended_citation": {
- "type": "string"
- },
- "recommended_workflows": {
- "type": "array"
- },
- "recovery_action": {
- "type": "string"
- },
- "research_use_only": {
- "type": "boolean"
- },
- "response_modes": {
- "type": "array"
- },
- "retryable": {
- "type": "boolean"
- },
- "server": {
- "type": "string"
- },
- "server_version": {
- "type": "string"
- },
- "success": {
- "type": "boolean"
- },
- "tool_count": {
- "type": "integer"
- },
- "tools": {
- "type": "array"
- }
- },
- "required": [
- "success"
- ],
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses no behavioral traits beyond the readOnlyHint annotation. It does not describe what the output contains, whether it is expensive, or any side effects. With annotations already covering safety, the description still fails to add context about the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single line, but it is under-specified rather than concise. It lacks front-loaded useful information and does not earn its place; it merely repeats the signature.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's purpose is unclear and there is an output schema, the description should at least state what capabilities are returned. Without this, an agent cannot understand the tool's functionality or interpret results. The description is completely inadequate for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description only lists parameter names without any additional meaning. The schema provides brief descriptions ('Detail level.', 'Mode.'), but these are minimal and the description does not enrich them. With 100% schema coverage, the baseline is 3, but the description adds zero value, so a 2 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is merely a function signature restating the tool name and parameter names, providing no explicit statement of what the tool does. 'get_server_capabilities' implies retrieval of server capabilities, but that is not stated; it is a tautology of the name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, no context, and no exclusions. The description offers nothing to help an agent decide between this and sibling tools like get_diagnostics or get_tolerance_landscape.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.