Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

JPL Sentry impact risk

jpl_sentry
Read-onlyIdempotent

Assess Earth impact risk with JPL Sentry data: fetch summary tables, single-object details, virtual impactors, or removed objects using filters like impact probability and Palermo Scale.

Instructions

Earth impact risk assessments from JPL Sentry: summary table, one object, virtual impactors, or removed objects.

Input Schema

NameRequiredDescriptionDefault
allNoVirtual-impactor mode: all VIs (combine with ip_min/ps_min/h_max to narrow).
desNoObject mode: designation, e.g. 29075 or 2011 AG5.
spkNoObject mode: SPK-ID.
h_maxNoSummary/VI mode: maximum absolute magnitude H.
limitNoReturn at most this many records from list modes. Applied by this server: Sentry has no limit parameter.
ip_minNoSummary/VI mode: minimum impact probability, e.g. 1e-5.
ps_minNoSummary/VI mode: minimum Palermo Scale value, e.g. -3.
removedNoList objects removed from Sentry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / all / description
      Previous value: -"Get all virtual impactors data"New value: +"Virtual-impactor mode: all VIs (combine with ip_min/ps_min/h_max to narrow)."
    • removedInput schema / properties / date_max
      Removed value: -{
-  "description": "End date (YYYY-MM-DD)",
-  "type": "string"
-}
    • removedInput schema / properties / date_min
      Removed value: -{
-  "description": "Start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • changedInput schema / properties / des / description
      Previous value: -"Object designation (e.g., '2011 AG5' or '29075')"New value: +"Object mode: designation, e.g. 29075 or 2011 AG5."
    • addedInput schema / properties / des / maxLength
      Added value: +100
    • addedInput schema / properties / des / minLength
      Added value: +1
    • changedInput schema / properties / h_max / description
      Previous value: -"Maximum absolute magnitude (size filter)"New value: +"Summary/VI mode: maximum absolute magnitude H."
    • changedInput schema / properties / ip_min / description
      Previous value: -"Minimum impact probability"New value: +"Summary/VI mode: minimum impact probability, e.g. 1e-5."
    • addedInput schema / properties / ip_min / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / ip_min / maximum
      Added value: +1
    • changedInput schema / properties / ip_min / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Return at most this many records from list modes. Applied by this server: Sentry has no limit parameter."
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / ps_min / description
      Previous value: -"Minimum Palermo Scale value"New value: +"Summary/VI mode: minimum Palermo Scale value, e.g. -3."
    • changedInput schema / properties / ps_min / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / removed / description
      Previous value: -"Get objects removed from Sentry monitoring"New value: +"List objects removed from Sentry."
    • changedInput schema / properties / spk / description
      Previous value: -"Object SPK-ID"New value: +"Object mode: SPK-ID."
    • addedInput schema / properties / spk / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / spk / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / spk / type
      Previous value: -"string"New value: +"integer"
  2. First observed

TDQS

B3.4/5.0
Behavior3/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, so the safety profile is covered. The description adds only the enumeration of result modes, which is modest added context; it says nothing about rate limits, upstream Sentry availability, or result size behavior (the server-side limit is only disclosed in the schema).

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?

A single compact sentence with the source and the mode list front-loaded; nothing is wasted. It is arguably too terse for eight interacting parameters, but there is no filler to trim.

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?

With eight optional parameters, no required fields, no output schema and mutually exclusive mode combinations, the description is only minimally sufficient: it names the modes but does not explain that parameters are mode-gated or how the modes relate to each other. The rich schema compensates, keeping this adequate rather than poor.

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% and the schema descriptions are unusually informative, including mode labels, examples (e.g. '29075 or 2011 AG5', '1e-5') and the note that limit is applied by this server. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 resource (Earth impact risk assessments from JPL Sentry) and enumerates the four output modes: summary table, single object, virtual impactors, removed objects. That is far more than a restated title. It does not, however, differentiate itself from the nearby jpl_scout or jpl_nhats siblings, which also concern impact risk, so an agent cannot route between them from this text alone.

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?

Listing the modes implies which parameter combinations to use, and the schema descriptions carry the actual mode mapping ('Object mode:', 'Summary/VI mode:'), but the description itself gives no when-to-use guidance, no prerequisites, and no statement of when to prefer a sibling such as jpl_scout. Usage is inferable rather than stated.

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