Skip to main content
Glama
Sign In
meteor-mcp

meteor-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Version Info

get_version_info
Read-onlyIdempotent

Returns the meteor-mcp server version and shower-list edition, enabling clients to verify compatibility and cite the data source.

Instructions

This server's version and the edition of the shower list it carries.

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 observedv0.4.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds only that the return includes the server version and a 'shower list' edition, which is modest extra context; it says nothing about format, caching implications, or whether the version changes during a session.

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?

It is short and front-loaded, which is good, but the phrasing 'the edition of the shower list it carries' is ambiguous enough that the single sentence does not earn its place cleanly. A clearer wording ('server version and meteor shower catalog edition') would be both concise and precise.

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

Completeness3/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 return values need not be spelled out, and zero parameters plus rich annotations reduce the burden. Still, the description leaves the key concept ('edition of the shower list') undefined, so an agent cannot fully know what it's getting beyond a vague version/edition pair.

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 there is nothing for the description to disambiguate; baseline 4 applies. The schema is trivially complete and the description does not need to explain inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'This server's version' identifies the resource, but there is no verb and the second clause, 'the edition of the shower list it carries,' is cryptic — it's unclear whether 'edition' means a data version, a catalog edition, or something else. An agent can guess this reports server/data version, but the purpose is stated vaguely rather than as a specific verb+resource.

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

Usage Guidelines2/5

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

No guidance whatsoever on when to call this versus the six meteor-related siblings (meteor_shower_info, meteor_source_info, etc.). No prerequisites, no exclusions. The agent must infer that this is for version/edition checks rather than meteor data lookups.

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