Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_star_system

Creates a new star system record linked to a cosmic structure, enabling astrophysics models to organize stellar data by parent structure.

Instructions

Create a new star system record associated with a cosmic structure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cosmic_structure_id": "<cosmic_structure_id>",
      "name": "<name>"
    },
    "name": "create_star_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the star system (e.g. 'TRAPPIST-1', 'Sirius')
themesNoThematic astrophysical tags (e.g. ['red dwarf', 'multi-planetary', 'habitable zone'])
descriptionNoScholarly description of stellar classification, mass, metallicity, and dynamics
cosmic_structure_idYesCosmic Structure ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that a record is created but does not disclose required permissions, whether the referenced cosmic structure must already exist, duplicate-name behavior, validation or failure modes, or what the operation returns.

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 single sentence is front-loaded and free of filler. It is efficient, though its brevity leaves out useful behavioral context rather than including unnecessary wording.

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 mutation tool with no annotations, four parameters, and no output schema, the description is too thin. It omits preconditions, side effects, error behavior, and return information that an agent would need to invoke it confidently.

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 the schema already explains all four parameters, including name, themes, description, and cosmic_structure_id. The description only restates the cosmic-structure association and adds no syntax, defaults, or constraints beyond the schema; a baseline 3 is appropriate.

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?

States a specific verb and resource ('Create a new star system record') and adds the association with a cosmic structure. It is clear, though it does not differentiate itself from sibling creation tools such as create_cosmic_structure or create_celestial_body.

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?

The phrase 'associated with a cosmic structure' implies that a cosmic_structure_id is required, but there is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent must infer usage from the schema alone.

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