Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

populate_cosmic_structure_star_systems

Generates and populates star systems for a specified cosmic structure using LLM generation, optionally waiting for discovery to finish.

Instructions

Discover and populate star systems for a specific cosmic structure via LLM generation.

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": {
      "id": "<id>"
    },
    "name": "populate_cosmic_structure_star_systems"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCosmic Structure ID
syncNoIf true, wait synchronously for star system discovery to finish

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 supplied, so the description carries the full behavioral burden and largely does not. It hints that output comes from LLM generation (implying nondeterminism and likely latency/cost), but never states that records are created in the database, whether existing star systems are preserved or overwritten, or what happens when sync=false. That is a significant gap for an unannotated mutation tool.

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 front-loaded sentence with no filler or redundancy. It is efficient, but so terse that the concision comes at the cost of the behavioral detail an agent needs.

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 two-parameter generative mutation tool with no annotations and no output schema, the description should disclose side effects, idempotency, and what is returned. It covers only the headline purpose, leaving key operational questions unanswered.

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%, with both 'id' (Cosmic Structure ID) and 'sync' (wait synchronously) documented in the schema, so the baseline is 3. The description adds no parameter-level meaning at all — it does not say what scope 'id' controls or what the result looks like under sync=true versus false.

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 names a specific verb pair (discover and populate) and a specific resource (star systems scoped to a cosmic structure), plus the generation mechanism. It is clear what the tool does, though it never contrasts itself with the sibling populate_star_systems_bulk, so the agent must infer the difference from the name alone.

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 when-to-use or when-not-to-use guidance is given. With siblings like populate_star_systems_bulk and populate_star_systems_batch, the description should say why one would target a single structure here rather than bulk-populating, but it offers nothing.

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