oddsky

fold

Phase-bins astronomical light-curve data by period to compute median depths, primary and secondary depths, and odd/even cycle comparisons that reveal period halving.

Instructions

Fold a series on a period: phase-binned medians, primary depth (phase 0) and secondary depth (phase 0.5) within +/- window_phase, the faintest bin away from the primary (a secondary at any phase, for eccentric orbits), and primary depth on even vs odd cycles (catches period halving).

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>",
      "series": "<series>",
      "period": "<period>",
      "t0": "<t0>"
    },
    "name": "fold"
  }
}

Input Schema

Name	Required	Description	Default
`t0`	Yes
`case`	Yes
`n_bins`	No
`period`	Yes
`series`	Yes
`window_phase`	No

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 provided, the description carries the full behavioral burden. It usefully discloses the computational behavior and output diagnostics, including phase-binned medians and even/odd cycle comparison, but it does not state whether the tool is read-only, whether it modifies the case, what permissions or data requirements exist, or how results are returned.

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 front-loaded with the core action and avoids filler, with every clause describing a meaningful computed diagnostic. It is dense and packed into one long sentence with nested parentheticals, which slightly reduces readability but does not waste words.

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 six-parameter analysis tool with no annotations, no output schema, and 0% schema description coverage, the definition is incomplete. It explains the folding outputs reasonably well, but does not provide enough parameter meaning or invocation context for an agent to call it confidently without guessing.

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%, so the description must compensate for six undocumented parameters. It partially explains 'period' and 'window_phase' through the phase-window discussion, but leaves 'case', 'series', 't0', and 'n_bins' unexplained, which is a substantial gap for required and defaulted parameters.

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 verb and resource ('Fold a series on a period') and enumerates the computed diagnostics: phase-binned medians, primary depth, secondary depth, faintest off-primary bin, and even/odd cycle depths. This is clear enough to distinguish the general operation, but it does not explicitly differentiate fold from siblings such as periodogram or eclipse_period.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives or exclusions. The phrase 'catches period halving' hints at one diagnostic use case, but an agent must infer when folding is preferable to running periodogram or other sibling analyses.

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