oddsky

ir_excess

Computes NEOWISE infrared excess relative to a baseline photosphere epoch, reporting per-band excess flux fractions and the excess blackbody temperature from the W1/W2 ratio.

Instructions

Infrared excess in NEOWISE over a baseline (photosphere) epoch: excess flux in each band as a fraction of the star, and the blackbody temperature of the excess from its W1/W2 ratio.

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": {
      "case": "<case>",
      "baseline_start": "<baseline_start>",
      "baseline_end": "<baseline_end>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "ir_excess"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes
`case`	Yes
`start`	Yes
`baseline_end`	Yes
`baseline_start`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 12, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the computation outputs and the W1/W2 temperature method, but it does not explain required data assumptions, units, handling of missing bands, or failure behavior.

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 description is a single dense sentence with no filler. It is front-loaded with the main computation and then explains the derived outputs, though it could be slightly more structured for a complex tool.

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?

This is a complex scientific computation with five required parameters, no annotations, and no output schema. The description explains what is calculated but leaves input formatting, data requirements, and operational assumptions undocumented, so it is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for five required parameters. The description mentions a baseline epoch and W1/W2 ratio, which loosely hints at baseline_start/baseline_end, but it never maps case, start, end, or date formats to their meaning.

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 scientific computation: IR excess in NEOWISE relative to a baseline photosphere epoch, including per-band excess flux fraction and a blackbody temperature derived from W1/W2. This is clear enough to distinguish the tool's core purpose, though it does not explicitly contrast with siblings such as wise_color or cross_band.

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 description does not say when to use this tool versus alternatives, nor does it state prerequisites or exclusions. Usage is only implied by the scientific context of measuring infrared excess.

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