Skip to main content
Glama
mitomap-link
by berntpopp

Get Diagnostics

get_diagnostics
Read-onlyIdempotent

Verify the pinned MITOMAP data release and inspect expected versus observed tags, digests, timestamps, and record counts. Use it to confirm the data version or diagnose upstream_unavailable errors.

Instructions

Report whether the pinned MITOMAP data release is materialized and verified: expected vs observed release tag and digest, upstream dump Last-Modified and SHA-256, MITOMAP edit dates and record counts. Use it to confirm the data version or diagnose an upstream_unavailable error. 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.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real context beyond them: it checks a pinned upstream release, compares expected vs observed values, and is the tool to reach for after an upstream_unavailable failure — consistent with openWorldHint. It stops short of saying whether a mismatch raises an error or is merely reported.

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?

Front-loaded with what is reported, then when to use it — a sensible order with no filler prose. The trailing 'Signature: get_diagnostics().' is mildly redundant given the empty input schema but does confirm the call shape.

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?

With no output schema, the description carries the burden of describing results, and it does so by enumerating the reported fields (tag, digest, Last-Modified, SHA-256, edit dates, counts). Only the response shape and failure/mismatch behavior remain unstated, which is a minor gap for a zero-parameter read-only tool.

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 no parameters, so the baseline is 4. The stated signature get_diagnostics() reinforces the zero-argument contract, though it adds little beyond the already-empty schema.

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?

States a specific verb and resource — reporting the materialization/verification state of the pinned MITOMAP data release — and enumerates exactly what is reported (release tag and digest, upstream Last-Modified and SHA-256, edit dates, record counts). This is unmistakably a diagnostics tool and cannot be confused with get_variant or search_variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete triggers: confirming the data version, or diagnosing an upstream_unavailable error. No explicit exclusions or named alternatives are provided, but the sibling tools are data-query tools, so the routing is clear enough without them.

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