Skip to main content
Glama
Sign In
io.github.qso-graph/ionis-mcp

io.github.qso-graph/ionis-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Version Info

get_version_info
Read-onlyIdempotent

Retrieve the running ionis-mcp service version and IONIS dataset revision to compare MCP deployments and detect version drift.

Instructions

Get ionis-mcp service version and upstream dataset version.

Returns the running PyPI version of ionis-mcp and the IONIS SourceForge dataset bundle revision in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. Beyond those, the description discloses what is actually returned (running PyPI version vs. dataset bundle revision) and that comparison can be done without leaving the MCP protocol — context the annotations do not carry.

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 the primary statement of what is returned, followed by the operational rationale. Two sentences are appropriate; there is mild restatement between 'upstream dataset version' and the SourceForge bundle sentence, but nothing wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not document return fields, and annotations cover the safety profile. What remains — why an agent would call this and what it means for fleet alignment — is fully supplied.

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 baseline is 4; the description correctly adds nothing misleading about inputs and instead spends its words on outputs and usage.

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 the exact resource (ionis-mcp service version plus upstream IONIS SourceForge dataset bundle revision) and the verb (get). This is clearly a metadata/diagnostic tool and cannot be confused with any sibling such as query_signatures or current_conditions.

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?

It states a concrete use case — confirming fleet alignment and detecting drift across MCP deployments by comparing service_version and spec_version. It does not explicitly say when not to use it or name alternatives, but no sibling plausibly overlaps, so the guidance is sufficient without exclusions.

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

Deploy Server

Other Tools