Skip to main content
Glama

Get Diagnostics

get_diagnostics
Read-only

Report runtime build, upstream request budget usage, cache hits, and latency metrics without calling cBioPortal, so you can monitor limits and troubleshoot performance.

Instructions

Report runtime state without calling cBioPortal: build, upstream request budget (today's usage vs the daily cap), cache hits and tool latency metrics. Signature: get_diagnostics().

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_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description earns credit for stating the non-obvious behavioral trait that this inspection incurs no upstream request (a real cost consideration for a budgeted API) and for listing what state is surfaced. It does not describe return formatting or whether metrics are cumulative or per-session.

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?

Two sentences, front-loaded with the action and the key cost-free property, followed by the payload contents. The trailing 'Signature: get_diagnostics().' repeats information already fully conveyed by the empty input schema and is wasted space.

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 zero-argument, read-only diagnostics tool with no output schema, the description covers what the agent needs: what state is reported and that no upstream call is made. Only minor gaps remain, such as the shape/units of the returned metrics, which the agent can discover from the actual response.

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?

With zero parameters the baseline is 4, and the 'Signature: get_diagnostics()' line correctly confirms the tool takes no arguments, reinforcing the empty schema. No further parameter meaning is needed.

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 names a specific verb ('Report runtime state') and enumerates the exact contents: build, upstream request budget with today's usage vs daily cap, cache hits, and tool latency metrics. The clause 'without calling cBioPortal' separates it from the sibling data-fetching tools (get_study, search_studies, get_gene_mutations), so an agent can tell this is the introspection tool rather than a data query.

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: the phrase 'without calling cBioPortal' hints that this call is free of upstream budget cost, which suggests checking it before heavy querying, but the description never states when to prefer it or what to do with the results. No exclusions or explicit alternatives are given.

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