Skip to main content
Glama
mitomap-link
by berntpopp

Get Server Capabilities

get_server_capabilities
Read-onlyIdempotent

Discover the mitomap-link MCP server's available tools, call signatures, variant notation rules, response modes, error codes, limits, data pin, license, and citation; use detail=full for usage notes.

Instructions

Return the mitomap-link discovery surface: tools with call signatures, argument aliases, response modes, accepted variant notations, status/plasmy/GenBank semantics, error codes, limits, data pin, license and citation. detail='full' adds the usage notes. Signature: get_server_capabilities(detail=).

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
detailNosummary (default) or full (adds usage notes).summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. Beyond that, the description adds real behavioral context: it enumerates exactly which artifacts come back (call signatures, alias tables, error codes, data pin, license/citation) and states that detail='full' adds usage notes. It stops short of describing response size, formatting, or MCP-level error behavior.

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 core purpose, then a dense itemization. The long slash-and-comma enumeration is efficient but visually flat, and the trailing 'Signature: get_server_capabilities(detail=)' largely repeats the schema.

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 one optional parameter and no output schema, the description carries the burden of explaining what comes back and does so comprehensively through its enumeration. It is complete enough for correct invocation; only the ordering vs. sibling tools and the response's size/shape remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already has an enum with a default and its own description, so the schema does the heavy lifting. The description restates the default and clarifies what 'full' actually adds (usage notes), which is a small but genuine semantic addition. Baseline 3 applies.

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 specific verb and resource are stated clearly: 'Return the mitomap-link discovery surface', followed by an enumeration of the artifacts returned (tools with call signatures, aliases, response modes, error codes, limits, license, citation). It is obviously a self-description/metadata tool, which implicitly separates it from the data-oriented siblings, though no sibling is named to make the contrast explicit.

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?

There is no explicit when-to-use guidance such as 'call this first to orient yourself' or when to prefer get_diagnostics or search_variants instead. The only conditional statement is about the detail flag, which is a parameter choice rather than a use-case rule. The discovery framing implies the intended usage, but the agent must infer it.

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