# chrono-parse

`station__temporal__chrono-parse` · external (needs EXECUTION_BACKEND_URL configured) · domain `temporal` · pv-relevance `non-pv`

supplied strftime pattern (e.g. "%Y-%m-%d %H:%M:%S").

> **Note:** This tool routes through an external execution backend. If `EXECUTION_BACKEND_URL` is unset on the server, calls return JSON-RPC error `-32603 "Tool execution backend not configured"`. Tools with `backend: native` execute in-process and are always callable.

## Agent metadata

- `idempotent`: unknown
- `read_only`: unknown
- `expected_latency_ms`: unknown (not yet contract-tested)
- `cost_tokens_estimate`: unknown

## Input schema

- `format` *string* — Optional strftime format string for naive datetimes (e.g. "%Y-%m-%d %H:%M:%S"). When omitted, RFC 3339 and ISO 8601 date are tried automatically.
- `input` *string* (required) — Datetime string to parse. Accepts RFC 3339 (e.g. "2026-02-25T14:30:00Z"), ISO 8601 date (e.g. "2026-02-25"), or naive datetime with an explicit format.

## Example call

```json
POST /api/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__temporal__chrono-parse",
    "arguments": {
      "input": ""
    }
  }
}
```

## Related

- [/tools](/tools) — all 3062 tools
- [/tools/temporal__chrono-parse](/tools/temporal__chrono-parse) — HTML page
- [/tools/temporal__chrono-parse/json](/tools/temporal__chrono-parse/json) — JSON form (agent-friendly)
- [/api/mcp](/api/mcp) — endpoint
- [/AGENTS.md](/AGENTS.md) — agent guide