Skip to main content
Glama

Get Server Capabilities

get_server_capabilities
Read-only

Retrieve cBioPortal server capabilities, including identifiers, limits, data version, licence handling, rate-limit policy, citations, and error codes.

Instructions

Describe this server: identifiers, limits, data version, licence handling, rate-limit policy, citations and error codes. Signature: get_server_capabilities().

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_server_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral value by promising exposure of rate-limit policy, licence handling and error codes — operational facts an agent needs — but it says nothing about the response shape or how that information is arranged, which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content list is front-loaded and dense, which is good, but the trailing function signature is pure waste on a zero-argument tool and is the least useful sentence in the definition. The enumeration is a flat run-on rather than structured, though it remains readable.

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 simple, zero-parameter metadata tool with no output schema, naming the categories of information returned is close to sufficient: an agent knows it can learn limits, versions, licences, rate limits, citations and error codes. The remaining gap is the form of the response, which the description cannot supply without an output schema.

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 takes zero parameters, so the schema carries the full parameter burden and there is nothing for the description to clarify. Baseline of 4 applies; the trailing 'Signature: get_server_capabilities().' adds nothing but is harmless.

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 gives a specific verb ('Describe') and resource ('this server') and enumerates what that description covers: identifiers, limits, data version, licence handling, rate-limit policy, citations and error codes. This clearly separates it from the data-oriented siblings like get_study or list_cancer_types, though it never explicitly contrasts itself with any of them.

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?

Usage is only implied: an agent infers this is a first-call/discovery tool that tells you server limits and policies before making other calls. There is no explicit when-to-use statement, no mention of when it is unnecessary, and no reference to alternatives.

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