Skip to main content
Glama
Sign In

OrbitStudio

by com.orbitstudio3d
OverviewDiscussionsAdmin

Star map link

star_map_link
Read-onlyIdempotent

Build a link that opens OrbitStudio Sky with the night sky over a place on Earth at a local date and time, as a 3D-printable star map plate. Use it for a birth, wedding or 'night we met' star map. Give a place name, which is looked up on OpenStreetMap, or latitude and longitude, which win when both are given. When a name matches more than one place, the tool lists them instead of choosing: ask the user which one they mean.

Input Schema

NameRequiredDescriptionDefault
dateYesLocal date, YYYY-MM-DD, 1900-01-01 to 2100-12-31.
timeNoLocal time, HH:MM 24-hour. Defaults to 21:00.21:00
labelNoOptional text engraved on the plate instead of the place name.
placeNoThe place on Earth, e.g. 'Amsterdam, Netherlands'; adding the region or country avoids a list of candidates. Looked up when latitude and longitude are not given. Also the label engraved on the plate (first 40 characters) unless label is given.
latitudeNoLatitude in degrees. Give it with longitude instead of a place name; it wins over one.
longitudeNoLongitude in degrees east (negative is west).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / label
      Added value: +{
+  "description": "Optional text engraved on the plate instead of the place name.",
+  "maxLength": 40,
+  "type": "string"
+}
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude in degrees."New value: +"Latitude in degrees. Give it with longitude instead of a place name; it wins over one."
    • changedInput schema / properties / place / description
      Previous value: -"Optional label engraved on the plate, e.g. 'Amsterdam, Netherlands'."New value: +"The place on Earth, e.g. 'Amsterdam, Netherlands'; adding the region or country avoids a list of candidates. Looked up when latitude and longitude are not given. Also the label engraved on the plate (first 40 characters) unless label is given."
    • changedInput schema / properties / place / maxLength
      Previous value: -40New value: +120
    • changedInput schema / required
      Previous value: -[
-  "latitude",
-  "longitude",
-  "date"
-]New value: +[
+  "date"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world access, so the description is not carrying that burden. It still adds real behavior: the OpenStreetMap lookup dependency, lat/long winning over place, and the crucial ambiguity case where the tool returns candidates instead of picking one.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the outcome, then inputs, then edge-case handling. Every sentence carries information an agent needs; nothing is padding.

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 correctly states that the return is a link and that ambiguous matches yield a list of candidates instead of a link. That covers the main return-value ambiguity for this tool, though it leaves minor details (exact link format, whether errors are surfaced) 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 description coverage is 100%, so every parameter is already documented in the schema, including the precedence of latitude/longitude and the place-as-label fallback. The description restates that precedence but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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: it builds a link that opens OrbitStudio Sky showing the night sky over a place at a local date/time as a 3D-printable star map plate. That is concrete enough to separate it from siblings like search_places or get_preview without opening a schema.

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 explicit use cases (birth, wedding, 'night we met') and the precedence rule for place vs. latitude/longitude. It also prescribes behavior for ambiguous place names (list them, ask the user), which is effectively when-to-do-what guidance. It stops short of naming an alternative tool for resolving ambiguous places.

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

All OrbitStudio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources