Supernova Cosmology MCP Server

describe_sn_dataset

Retrieve full details of a supernova dataset, including products, units, conventions, URLs, and citation, by providing its name from the list tool.

Instructions

Full description of one dataset: products, units, conventions, URLs, citation.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Dataset key from the list tool.

Output Schema

Name	Required	Description	Default
`files`	Yes
`status`	Yes
`message`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden alone. 'Description of one dataset' plus the enumerated content types makes clear this is a non-mutating lookup and tells the agent roughly what comes back, but it says nothing about permissions, failure behavior for unknown keys, or cost/latency.

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 terse sentence that front-loads the primary purpose and then lists the returned content areas. Nothing is wasted, though the fragment style reads slightly telegraphic rather than as polished prose.

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

Completeness4/5

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

For a one-parameter read tool with an output schema present, the description covers what the call yields and implies the sequencing from the list tool. Return-value structure is handled by the output schema, so no real gap remains for an agent deciding how to call it.

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 the single parameter is documented in the schema as 'Dataset key from the list tool', which already conveys the key format source. The description adds only the singular 'one dataset' framing on top of that, matching the baseline for fully covered schemas.

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 resource and scope: a full description of one dataset, enumerating the kinds of content returned (products, units, conventions, URLs, citation). This is clearly distinguishable from the sibling list_sn_datasets, though the description never names that sibling explicitly to reinforce the contrast.

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?

No explicit when-to-use or when-not-to-use statement appears in the description. The usage pattern is only implied by the pairing with list_sn_datasets and by the schema note that the argument is a 'Dataset key from the list tool', so an agent can infer the list-then-describe sequence but is not told it.

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