Tanod MCP Server (Deprecated)

by dev.tanod

Overview Discussions Admin

This connector has been deprecated

The correct URL is https://tanod.dev/mcp and NOT https://tanod.dev/mcp/ (CORRECT: NO TRAILING SLASH)

Correct Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod

WRONG Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod-mcp-server/

skypeek: upcoming asteroid close approaches

asteroid_close_approaches

Read-onlyIdempotent

skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with its 3-sigma range, relative velocity, absolute magnitude and diameter (published or a rough range). Data: NASA/JPL Solar System Dynamics close-approach API (US Government work); no endorsement by NASA or JPL is implied. At most 100 approaches per answer. Not an impact-risk assessment. Cached up to an hour. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/asteroid-close-approach-api.html

Input Schema

Name	Required	Description	Default
`days`	No	Look-ahead window in days (1-30).
`dist_max_au`	No	Largest nominal miss distance in au (0.0001-0.2; 0.05 au is about 19.5 lunar distances).

Output Schema

Name	Required	Description
`days`	No
`note`	No
`count`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`stale`	No
`cached`	No
`source`	No
`truncated`	No
`approaches`	No
`attribution`	No
`dist_max_au`	No
`cache_seconds`	No
`total_matches`	No
`dist_max_lunar`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 3, 2026

addedOutput schema / properties / approaches / items / properties / approach_time_tdb
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / approaches / items / properties / diameter_m
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / approaches / items / properties / distance_max_au
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / approaches / items / properties / distance_min_au
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

addedOutput schema / properties / approaches / items / properties / estimated_diameter_m

Added value: +{
+  "properties": {
+    "max": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "min": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: states the 100-approach cap, one-hour cache, sub-second latency, 503 upstream_unavailable behavior with no charge, pricing and free-tier limits, and explicitly disclaims impact-risk assessment. This is exactly the operational context annotations can't carry.

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 purpose and sibling routing are front-loaded, and the remaining clauses (cache, cap, error, price, docs) are each operationally distinct. It is dense but every sentence carries information, though the legal attribution clause is slightly heavy.

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

Completeness5/5

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

Even though an output schema exists, the description names the returned fields (designation, approach time, 3-sigma distance, velocity, magnitude, diameter) and clarifies the diameter may be a rough range. For a low-parameter paid API tool, nothing an agent needs before calling is missing.

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 100% and both parameter defaults and the 0.05 au ≈ 19.5 lunar-distance conversion already appear in the schema, so the description largely restates them. It adds only the framing of 'upcoming' window semantics; baseline 3 is appropriate.

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 ('List asteroid and comet close approaches to Earth') with scope (1-30 days, max miss distance), and explicitly distinguishes itself from the sibling get_space_weather. An agent can identify this tool without opening the 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?

Names the alternative for a neighboring domain ('For space weather use get_space_weather') and bounds the use case by window and distance. It lacks explicit when-not-to-use guidance beyond that single routing pointer, so it falls short of a full 5.

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

All Tanod MCP Server (Deprecated) tools Inspect

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

Need Help?