Skip to main content
Glama
Sign In

Horizons Nasa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Lookup

lookup
Read-onlyIdempotent

Resolve an object name → SPK id.

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultNoLookup results containing matched objects
signatureNoAPI signature information

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Mars"
+  },
+  {
+    "query": "ISS"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Response from JPL Horizons lookup API",
+  "properties": {
+    "result": {
+      "description": "Lookup results containing matched objects",
+      "properties": {
+        "results": {
+          "description": "Array of matched objects",
+          "items": {
+            "properties": {
+              "designation": {
+                "description": "Object designation",
+                "type": "string"
+              },
+              "id": {
+                "description": "SPK ID of the object",
+                "type": "string"
+              },
+              "name": {
+                "description": "Object name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total_results": {
+          "description": "Total number of results found",
+          "type": "integer"
+        },
+        "truncated_results": {
+          "description": "Whether results were truncated",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "signature": {
+      "description": "API signature information",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the specific transformation (name to ID) but no additional behavioral traits beyond what annotations convey.

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?

The description is a single, succinct sentence that efficiently communicates the tool's core function with no unnecessary words.

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?

For a simple lookup, the description is minimally adequate given the presence of annotations and an output schema. However, it lacks usage guidance and fails to mention what happens when the name is not found (e.g., returns null/empty).

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 coverage is 0%, so the description must explain parameters. It implies that 'query' is an object name via the examples (Mars, ISS), but does not explicitly describe the parameter's purpose or constraints. This provides partial compensation.

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 clearly states the action (resolve) and the mapping from object name to SPK id. It is specific and distinguishes this tool from siblings that perform more complex operations like comparison or entity profiling.

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 provided on when to use this tool versus alternatives like resolve_entity, entity_profile, or compare_entities. The description does not mention trade-offs or prerequisites.

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

All Horizons 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