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

Grid Info

grid_info
Read-onlyIdempotent

Convert a 4- or 6-character Maidenhead grid square to latitude/longitude and optionally compute solar elevation with day/twilight/night classification for a given UTC hour and date.

Instructions

Decode a Maidenhead grid to lat/lon and compute solar elevation.

Converts a 4-char or 6-char Maidenhead grid square to geographic coordinates. If hour is provided, computes solar elevation angle with day/twilight/night classification.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grid": "<grid>"
    },
    "name": "grid_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridYesMaidenhead grid (4-char like "DN13" or 6-char like "DN13la")
hourNoUTC hour (0-23) for solar elevation calculation
monthNoMonth (1-12) for solar elevation (used if day_of_year not given)
day_of_yearNoDay of year (1-366) for precise solar elevation

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavior beyond those hints: optional solar elevation calculation and day/twilight/night classification, which helps an agent understand conditional output.

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?

The description is short and front-loads the main purpose. The second sentence repeats the 4-char/6-char conversion point from the first, but the redundancy is minor and the conditional solar behavior is clearly stated.

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?

An output schema exists, annotations cover safety and idempotency, and all parameters are documented in the schema. The description supplies the key conditional behavior for solar elevation, making the definition complete enough for invocation.

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 description coverage is 100%, so the schema already documents grid, hour, month, and day_of_year in detail. The description reinforces that hour triggers solar elevation and that grid may be 4-char or 6-char, but it does not add much beyond the structured parameter descriptions.

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 description uses a specific verb and resource: decode a Maidenhead grid to lat/lon and optionally compute solar elevation. It is clear what the tool does, but it does not explicitly distinguish itself from solar-related siblings like solar_correlation or solar_history.

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?

The description implies usage by saying solar elevation is computed if hour is provided, and it mentions 4-char versus 6-char grids. However, it does not state when to choose this tool over solar_correlation, solar_history, or dark_hour_analysis.

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