Skip to main content
Glama

Mast Nasa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Lookup Name

lookup_name
Read-onlyIdempotent

Resolve target name → coords.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
resolvedCoordinateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / Resolving
      Removed value: -{
-  "description": "Array of resolved target coordinates",
-  "items": {
-    "properties": {
-      "RA": {
-        "description": "Right Ascension in degrees",
-        "type": "number"
-      },
-      "dec": {
-        "description": "Declination in degrees",
-        "type": "number"
-      },
-      "name": {
-        "description": "Resolved target name",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / resolvedCoordinate
      Added value: +{
+  "items": {
+    "properties": {
+      "cacheDate": {
+        "type": "string"
+      },
+      "cached": {
+        "type": "boolean"
+      },
+      "canonicalName": {
+        "type": "string"
+      },
+      "decl": {
+        "type": "number"
+      },
+      "majorAxis": {
+        "type": "number"
+      },
+      "minorAxis": {
+        "type": "number"
+      },
+      "objectType": {
+        "type": "string"
+      },
+      "positionAngle": {
+        "type": "number"
+      },
+      "ra": {
+        "type": "number"
+      },
+      "radius": {
+        "type": "number"
+      },
+      "resolver": {
+        "type": "string"
+      },
+      "resolverTime": {
+        "type": "number"
+      },
+      "searchRadius": {
+        "type": "number"
+      },
+      "searchString": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / status
      Added value: +{
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "M31"
+  },
+  {
+    "name": "Andromeda Galaxy"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "Resolving": {
+      "description": "Array of resolved target coordinates",
+      "items": {
+        "properties": {
+          "RA": {
+            "description": "Right Ascension in degrees",
+            "type": "number"
+          },
+          "dec": {
+            "description": "Declination in degrees",
+            "type": "number"
+          },
+          "name": {
+            "description": "Resolved target name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral detail beyond the basic function – no mention of matching behavior, potential ambiguity failures, return format, or any constraints. With annotations carrying the safety profile, the description contributes minimal extra transparency.

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 a single, front-loaded sentence with no fluff. It is appropriately concise for a tool with one parameter, though it may be too terse to be fully helpful. Still, conciseness and structure are strong.

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

Completeness2/5

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

For a one-parameter tool with an output schema, the description is extremely minimal. It lacks any guidance on valid input format, failure modes, or how this tool fits among the 38 siblings. Given the presence of many similar lookup tools, this is insufficient for reliable selection and invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for parameter semantics. It only says 'target name', which merely restates the property name, without clarifying accepted formats, catalog conventions, or ambiguity handling. The schema's examples (M31, Andromeda Galaxy) are not referenced in the description.

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 states a specific verb ('Resolve'), resource ('target name'), and result ('coords'), making the tool's purpose clear. It does not explicitly distinguish from sibling tools like `resolve_entity` or `cone_search`, but the output 'coords' is a clear differentiator.

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 is given on when to use this tool versus the many siblings such as `resolve_entity`, `mission_search`, or `search_within`. There are no conditions, exclusions, or alternative suggestions, leaving the agent to infer usage context entirely.

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

All Mast Nasa 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