# WritersLogic business agents (remote · agents.writerslogic.com)

Medical-bill audit, chargeback, contract terminator, lead enrichment, filing integrity.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agents.writerslogic.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business.md), [page](https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business)

## Channel facts

- Endpoint: `https://agents.writerslogic.com/mcp/business`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 95 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 21511 tokens (~226/item across 95 items; 95 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "storage-charge-clock" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 96 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the WritersLogic business agents MCP server?

WritersLogic business agents is a hosted endpoint at https://agents.writerslogic.com/mcp/business, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-writerslogic-agents-writerslogic-business 'https://agents.writerslogic.com/mcp/business'
```

### Cursor

```json
{
  "mcpServers": {
    "com-writerslogic-agents-writerslogic-business": {
      "url": "https://agents.writerslogic.com/mcp/business"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-writerslogic-agents-writerslogic-business": {
      "type": "http",
      "url": "https://agents.writerslogic.com/mcp/business"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-writerslogic-agents-writerslogic-business]
url = "https://agents.writerslogic.com/mcp/business"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-writerslogic-agents-writerslogic-business": {
      "type": "remote",
      "url": "https://agents.writerslogic.com/mcp/business",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-writerslogic-agents-writerslogic-business --url 'https://agents.writerslogic.com/mcp/business' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-writerslogic-agents-writerslogic-business:
    url: "https://agents.writerslogic.com/mcp/business"
```

### Netclaw

```json
{
  "McpServers": {
    "com-writerslogic-agents-writerslogic-business": {
      "Transport": "http",
      "Url": "https://agents.writerslogic.com/mcp/business"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-writerslogic-agents-writerslogic-business -t streamable-http -u 'https://agents.writerslogic.com/mcp/business'
```

### Other

```json
{
  "mcpServers": {
    "com-writerslogic-agents-writerslogic-business": {
      "type": "http",
      "url": "https://agents.writerslogic.com/mcp/business"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 63, +1)

- [cosmetic] “storage-charge-clock” reworded the description of “currency”
- [cosmetic] “storage-charge-clock” reworded the description of “freeCounting”
- [cosmetic] “storage-charge-clock” reworded the description of “freeDays”
- [cosmetic] “storage-charge-clock” reworded the description of “receivedOn”
- [cosmetic] “storage-charge-clock” reworded the description of “releasedOn”

### 2026-11-18 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 60)

First indexed and scored.

## MCP tools (95)

### `lead-enrichment` (~73 tokens)

Autonomous Lead Enrichment — Scrapes a company homepage, deduces its value proposition and buyer persona, and drafts a targeted B2B cold email.

Input parameters:

- `senderContext` (string): What you sell, used to tailor the pitch.
- `url` (string, required): Company homepage URL; https:// is assumed if omitted.

### `competitor-battlecard` (~164 tokens)

SaaS Pricing & Competitor Battlecard Spy — Reads up to 3 competitor sites (homepage and pricing page, fetched in parallel) and returns a deal battlecard in under a minute: a verdict headline with confidence, pricing tiers whose amounts are checked against the page text, a scenario cost comparison computed in code, hidden fees and limits, landmine questions, objection handling, wedge features and a talk track. If a site or model step fails

Input parameters:

- `competitorUrls` (array, required): Competitor homepage or pricing URLs. A same-site pricing page is discovered automatically.
- `ourProductDescription` (string, required)
- `scenario` (object): Optional deal size used to compute monthly and annual cost per verified tier: seats for per-seat prices, monthlyVolume for usage prices.

### `medical-bill-auditor` (~347 tokens)

Medical Bill Upcoding & Overcharge Slasher — Paste an itemized hospital or physician bill and get a decision first: dispute it or not, the estimated dollars above a defensible price, and a dispute letter ready to send. Flags E/M upcoding, NCCI unbundling, duplicates and unit errors line by line, prices professional claims against the CMS physician fee schedule, checks the No Surprises Act self-pay dispute deadline, and lists the letter's pla

Input parameters:

- `accountNumber` (string)
- `billReceivedDate` (string): Date the initial bill was received; used for the 120-day dispute deadline.
- `billText` (string): Alternative to lineItems: paste the itemized bill, one line item per line, e.g. "99285  EMERGENCY DEPT VISIT LVL 5   1   $3,250.00". Lines with a CPT/HCPCS code and a dollar amount are read in code;…
- `claimType` (string): Physician (CMS-1500) or hospital/facility (UB-04) bill. Medicare physician fee schedule benchmarks apply only to professional claims.
- `coverage` (string): Determines which No Surprises Act protections can apply.
- `facilityName` (string)
- `facilityType` (string, required)
- `goodFaithEstimateAmount` (number): Good Faith Estimate received (self-pay).
- `lineItems` (array)
- `patientName` (string)
- `patientState` (string)
- `visitSummary` (string): What actually happened: symptoms, duration, tests, treatment.

### `chargeback-fighter` (~228 tokens)

E-Commerce Chargeback Representment Builder — Tells a merchant whether to fight or accept a card dispute: scores win probability against the network rubric for the reason code (Visa, Mastercard, Amex, Discover), runs deterministic Visa CE3.0 eligibility and invalid-dispute checks, computes expected recovery net of the contest fee and days to the deadline, and returns a processor-ready submission (summary under 4,000 characters, evidence field

Input parameters:

- `disputeDate` (string)
- `disputeFeeUsd` (number): Fee your processor charges to contest the dispute and does not return on a loss; used to net the expected value.
- `evidence` (object, required)
- `network` (string, required)
- `orderDetails` (object, required)
- `reasonCode` (string, required): e.g. 10.4, 13.1, 13.3 (Visa); 4837, 4853, 4855 (Mastercard).
- `responseDeadline` (string): Deadline shown in your processor's dispute dashboard (YYYY-MM-DD); days remaining are computed from it.

### `contract-terminator` (~290 tokens)

Dark Pattern Contract & Subscription Exit Lawyer — Paste a contract or Terms URL and get the decision first: send notice by a computed date, or the window has passed. Quotes auto-renewal, notice-window and early-termination traps verbatim, computes the renewal and last-notice dates in code, estimates the renewal cost you avoid from your fee, maps the exit to ROSCA, state automatic-renewal laws and EU/UK consumer law with links, and drafts a notice

Input parameters:

- `accountIdentifier` (string)
- `annualFee` (number): What you pay per year, USD, if billed annually. Use monthlyFee or annualFee.
- `contractStartDate` (string)
- `contractText` (string)
- `customerName` (string)
- `customerType` (string)
- `earlyTerminationFeeUsd` (number): Early-termination fee the vendor says you owe, USD, if any.
- `monthlyFee` (number): What you pay per month, USD. Used to compute the dollars at stake.
- `reasonForExit` (string, required)
- `signupMethod` (string)
- `termsUrl` (string): Terms of Service or cancellation policy URL. Provide termsUrl or contractText.
- `userJurisdiction` (string, required): e.g. California, New York, EU (Germany), UK.
- `vendorName` (string, required)

### `tariff-engineer` (~230 tokens)

Global Customs & Tariff Engineering Optimizer — Classifies a product under the HTS with GRI reasoning and verifies the code and general (MFN) rate against the live USITC schedule, flags when a specific sibling subheading may outrank the chosen residual one, separates lower-duty options from reclassification risk with dollar exposure, lists lawful physical tariff-engineering changes, and drafts an accurate commercial invoice description. Leads w

Input parameters:

- `currentHtsCode` (string)
- `customsValueUsd` (number): Entered value, used to estimate duty and savings.
- `destinationCountry` (string, required)
- `importStateOfAssembly` (string)
- `intendedUse` (string, required)
- `materialsBreakdown` (array, required)
- `originCountry` (string, required)
- `productDescription` (string): Construction, dimensions, how it works, packaging.
- `productName` (string, required)
- `productUrl` (string): Public product or spec-sheet page. Its text is read to supplement productDescription; if it cannot be read the request still succeeds and says so in warnings.

### `accessibility-patcher` (~142 tokens)

ADA / WCAG Lawsuit Shield & DOM Auto-Patcher — Returns a FAIL / REVIEW / PASS verdict for a page's HTML (pasted or fetched from a URL) against the WCAG failures most cited in ADA demand letters: alt text, form labels, unnamed buttons and links, lang, headings, landmarks, skip links, zoom. Each issue carries a CSS selector, source line and fix, with a top-five list, a SARIF 2.1.0 log, a litigation risk score, per-element patched HTML and an int

Input parameters:

- `html` (string)
- `url` (string): Page to audit. Provide url or html.

### `audit-public-record` (~311 tokens)

OnRecord statutory clock & redaction auditor — Audits an agency's public-records response and leads with a decision (late, redaction problems, incomplete, pending or no violation found). Computes the statutory response deadline and days late (California CPRA, with the court-day calendar and § 7922.535 extension rules), flags redactions without an exemption citation, passages redacted in one document but readable in another, referenced attachme

Input parameters:

- `agencyName` (string): Agency that received the request; fills the follow-up letter.
- `asOfDate` (string): Observation date when responseDate is omitted; defaults to today (UTC).
- `documents` (array, required)
- `extensionNotices` (array)
- `gapThresholdDays` (integer): Report gaps between dated events longer than this (default 30).
- `jurisdiction` (string, required): OnRecord jurisdiction code. Only "CA_CPRA" (alias "US-CA") has a statute table; any other value returns clock "unknown_jurisdiction" while document checks still run.
- `requestDate` (string, required): Date the agency received the request (YYYY-MM-DD or RFC 3339; read in the offset written).
- `requestReference` (string): The agency's request or tracking number, for the follow-up letter.
- `requesterName` (string): Your name, for the follow-up letter signature.
- `responseDate` (string): Date of the agency's determination/response. Omit if none yet.

### `reconcile-ledger` (~464 tokens)

Exact Ledger Reconciler — Explains which charges, refunds and fees make up a Stripe, PayPal or bank payout, with an exact solver instead of a model: subset-sum over integer minor units (meet-in-the-middle, DP, branch-and-bound) across candidate fee schedules (percentage + fixed, tiers, caps), withholding, FX rates and rounding conventions (half-up, half-even, truncate; per line or on the total). Paste a Stripe balance or p

Input parameters:

- `conventions` (object): Restrict the conventions searched (default: all rounding modes x both scopes x both FX date policies).
- `crossCheck` (boolean): Run two independent LLM translations and keep only rows both produced (default true).
- `defaultCurrency` (string): Currency for text rows that state none.
- `feeSchedules` (array): Candidate fee schedules; the solver reports which one reconciles each settlement. Omit for no fees.
- `fxRates` (array): Direct rates only (1 from = rate to). The latest rate dated on or before the reference date applies; an undated rate is the fallback.
- `items` (array): Ledger lines. Amounts are signed (refunds and disputes negative) strings in major units, e.g. "1234.56".
- `limits` (object)
- `maxLagDays` (integer): An item may settle at most this many days after its date.
- `nearMissToleranceMinor` (integer): Largest residual searched when reporting the closest near-miss for an unmatched settlement.
- `settlements` (array): Payouts or bank settlement totals to explain.
- `text` (object): Messy source text for collections not given structurally. A CSV with a header (Stripe balance or payout-reconciliation export, PayPal activity export, bank statement) is parsed by code with no model,…
- `toleranceMinor` (integer): Accepted |residual| per settlement in minor units (default 0 = exact).
- `withholdings` (array)

### `filing-integrity-check` (~296 tokens)

SEC Filing Integrity Check: XBRL Footing, Tie-Outs, Revisions — Before a figure from a US 10-K or 10-Q is quoted, re-checks it with exact integer arithmetic on SEC XBRL data: balance sheet identity (including noncontrolling and temporary equity), net income bridge, cash flow to balance sheet cash tie-out with restricted cash and roll-forward, EPS recomputation, every calculation-linkbase relationship the filing declares, and same-period values that a later 10-

Input parameters:

- `accession` (string): Accession number of a 10-K or 10-Q, e.g. 0000320193-25-000079. Give this or fiscal_year with period.
- `checks` (array): Checks to run; default all six.
- `cik` (string): SEC CIK, digits only.
- `fiscal_year` (integer): Fiscal year of the filing's DocumentFiscalYearFocus.
- `period` (string): FY selects the 10-K; Q1 to Q3 select 10-Qs (there is no Q4 filing).
- `rounding_mode` (string): exact: any nonzero difference fails. reported_precision (default): differences within half a unit of the filing's reporting scale per rounded figure pass and are flagged.
- `ticker` (string): Exchange ticker, e.g. AAPL or BRK.B. Give exactly one of ticker or cik.

### `open-badges-verifier` (~328 tokens)

Open Badges 2.0 / 3.0 credential verifier — Verifies an Open Badges credential end to end and says what could and could not be confirmed. Accepts an Open Badges 3.0 credential (JSON with an eddsa-jcs-2022 proof, or a VC-JWT signed with EdDSA, ES256 or RS256), an Open Badges 2.0 assertion (hosted, or signed as an RS256 JWS), a hosted-assertion URL, or a baked PNG or SVG image. Checks the 2.0/3.0 required fields, the issuance and expiry windo

Input parameters:

- `credential`: The credential or assertion as a JSON object (or the same as a JSON string, or a compact JWS string).
- `image` (string): A baked badge image, base64 (data URLs accepted): a PNG with an openbadges iTXt chunk, or an SVG with an openbadges:assertion or openbadges:credential element. Up to 6 MB decoded.
- `jws` (string): A compact JWS: an Open Badges 3.0 VC-JWT or an Open Badges 2.0 signed assertion.
- `recipientIdentity` (string): Optional: the recipient's email or other identity to compare against the badge's recipient, including salted sha256$ and md5$ hashes.
- `url` (string): https URL of a hosted Open Badges 2.0 assertion or a hosted 3.0 credential.

### `redact-text` (~480 tokens)

Selective PII redaction with a self-check — Redacts detected personal data at the level you choose and rescans the output with the same rules. This self-check does not prove that all personal data is gone. Pick a level: 1 government identifiers (SSN, ITIN, EIN, UK NINO, Canadian SIN, driver's license, passport), 2 adds dates of birth, 3 adds street addresses and phone numbers, 4 adds person names and email addresses. Then switch single cate

Input parameters:

- `categories` (array): Exact set of categories to redact; replaces the level preset when given.
- `exclude` (array): Categories to remove from the level preset.
- `include` (array): Categories to add to the level preset.
- `keep` (array): Strings that must never be redacted, such as your own email address or company name. Case-insensitive, whole match.
- `level` (integer): Cumulative preset, default 1. 1: government identifiers (SSN, ITIN, EIN, UK NINO, Canadian SIN, driver's license, passport); 2: level 1 plus dates of birth; 3: level 2 plus street addresses and phone…
- `minDigitRun` (integer): Also redact every run of at least this many digits (spaces, dots and hyphens between digits count as part of the run). This is the number of digits, not the numeric value.
- `style` (string): label (default): [REDACTED:SSN]. generic: [REDACTED]. numbered: [PERSON_1], same value same number. last4: [REDACTED:SSN:*6789] for numeric identifiers; this discloses the last four characters.
- `terms` (array): Words or phrases to redact wherever they appear (business names, project names, people you already know). Case-insensitive.
- `text` (string, required): The document text to redact (plain text, Markdown, CSV, JSON or HTML source).
- `useModel` (boolean): Add a language-model pass for names, organizations and addresses (when those categories are on). Sends the text, up to 60000 characters, to the configured model provider. Default false.

### `literary-agent-scout` (~182 tokens)

Literary Agent Scout: quoted wish-list matches with query status and fee checks — For an author with a book to query, finds literary agents and agencies on the agencies' own websites, reads their guidelines and agent bios, and ranks them against your pitch. Every fit claim carries a sentence quoted verbatim from the agent's page (quotes not found on the page are dropped), each agent shows whether the page says queries are open or closed with the retrieval time, and any agency p

Input parameters:

- `discover` (boolean): Search the web for more agencies (default true). Set false to check only the pages you supplied.
- `manuscript` (object, required)
- `max_results` (integer): Default 5.
- `pages` (array): Agency submission, wish-list or agent-bio pages you already found. They are read and checked like the ones found by search.

### `property-risk` (~221 tokens)

Property Hazard & Site Risk Report — Before an agent recommends, underwrites or screens a US property, reads free public federal hazard data for a street address or lat/lon: Census geocode, FEMA National Flood Hazard Layer flood zone, SFHA status and base flood elevation, USGS ASCE 7-22 seismic design values, FEMA National Risk Index tract ratings (wildfire, hurricane, tornado and more), OpenFEMA county disaster declarations for 10 y

Input parameters:

- `address` (string): US street address with city and state or ZIP, e.g. 1111 Lincoln Rd, Miami Beach, FL 33139. Give this or lat with lon.
- `intended_use` (string): Optional. Reweights the score: residential counts environmental proximity 1.5x, industrial 0.5x, development counts flood and seismic 1.5x.
- `lat` (number): Latitude in WGS84 degrees; give with lon instead of address.
- `lon` (number): Longitude in WGS84 degrees; give with lat.

### `farmland-soil-report` (~174 tokens)

Farmland Soil, Water & Drought Report — Before buying, leasing or planting a US parcel, reads the USDA NRCS soil survey at a point (lat/lon or US address): map unit, prime farmland class, land capability class and subclass, drainage, hydric rating, flooding and ponding frequency, water table and bedrock depth, slope, pH, organic matter, available water capacity (percent-weighted across components) and building-site ratings with shrink-s

Input parameters:

- `address` (string): US street address, geocoded by the US Census geocoder.
- `lat` (number): WGS84 latitude. Give lat with lon, or address.
- `lon` (number): WGS84 longitude.
- `use` (string): Intended use to rate. Omit to rate all four.

### `property-violations-history` (~267 tokens)

Property Code-Violation & Lien History (Open-Data Cities) — Before buying, leasing or insuring a US property, reads the city's own open-data code-enforcement records for one address (or a NYC BBL/BIN) and returns normalized violations with date opened, category, description, open/closed status, source severity class and record URL; deterministic counts by status, category and year; days since the latest violation; the longest repeat-citation streak (citati

Input parameters:

- `address` (string): US street address with city and state, e.g. '447 21st Ave, San Francisco, CA 94121'. Give exactly one of address, bbl or bin.
- `bbl` (string): NYC borough-block-lot, 10 digits.
- `bin` (string): NYC building identification number, 7 digits.
- `city` (string): City, when not inside address. For NYC a borough name (Brooklyn, Queens, ...) narrows the match.
- `lookback_years` (integer): Years of history to read (default 10).
- `state` (string): Two-letter state, when not inside address.
- `zip` (string): ZIP code (informational; not used to widen a match).

### `regional-economy-brief` (~258 tokens)

Regional Economy & Trade Brief — Given a US state, county or metro (name, FIPS or CBSA), an industry (NAICS code or description) and a role (retailer, logistics, cfo, lender, other), reads BLS LAUS and QCEW, FRED (state employment, house prices, goods exports and imports, regional CPI), Census Building Permits and USAspending live, then computes levels, year-over-year and three-year changes, location quotient, z-scores against th

Input parameters:

- `industry` (string, required): NAICS code (44-45, 722, 4841) or a plain description ("restaurants", "trucking").
- `lookbackYears` (integer): Years of history used for z-scores (default 5).
- `region` (string, required): A US state, county or metropolitan area by name ("Ohio", "Travis County, TX", "Phoenix metro"), state FIPS (39), county FIPS (48453) or metro CBSA code (38060).
- `regionType` (string): Disambiguates a name that is both a county and a metro or state.
- `role` (string, required): Who the brief is for.

### `infrastructure-pipeline-brief` (~243 tokens)

Grid, Tower & Infrastructure Pipeline Near a Site — Screens a US site (latitude/longitude or Census-geocoded address) within a radius (default 10, max 50 miles) using primary public data: operating and planned generators and storage from EIA Form 860M, active interconnection-queue entries from MISO, CAISO, NYISO and ERCOT matched at county level, FCC Antenna Structure Registration towers, and HIFLD transmission lines and substations. Code computes

Input parameters:

- `address` (string): US street address, geocoded with the Census Bureau geocoder. Used when latitude/longitude are absent.
- `focus` (string): Which screening signals to emphasise. Default general.
- `latitude` (number): WGS84 latitude of the site (United States and territories). Give latitude and longitude together, or address.
- `longitude` (number): WGS84 longitude of the site.
- `radius_miles` (number): Search radius in miles (default 10, clamped to at most 50).
- `window_years` (integer): Window for capacity added within the radius (default 3 years).

### `minor-units` (~128 tokens)

ISO 4217 minor units: decimal amount to integer minor units and back — Converts up to 200 money amounts between decimal strings and integer minor units (cents, yen, fils) using the ISO 4217 exponent from the SIX Group list, for an agent about to send an amount to a payment API. Returns the exponent, the integer minor amount and the canonical decimal string; JPY is 0, KWD and BHD are 3, CLF is 4. An amount with more fraction digits than the currency allows fails with

Input parameters:

- `items` (array, required)

### `cash-rounding` (~141 tokens)

Cash rounding to the smallest payable coin (CHF, CAD, SEK, AUD or a caller rule) — Rounds up to 100 final cash totals to the smallest payable increment, for an agent computing what a customer actually pays in cash or the change owed. Built-in rules exist only for currencies with an official source: CHF 0.05 (Münzverordnung SR 941.101), CAD 0.05 (Government of Canada), SEK 1 (Lag 1970:1029), AUD 0.05 (Consumer Protection WA); any other currency needs a caller increment. Rounds th

Input parameters:

- `items` (array, required)

### `allocate` (~346 tokens)

Split a money amount into parts that sum exactly to the total — Splits one signed amount into up to 500 parts by weights (or equal parts), in integer minor units of its currency, for an agent dividing a bill, a refund, a fee or a tax. Each share is rounded under the declared mode, then the leftover minor units are assigned by the declared remainder policy, so the parts always sum to the total exactly. Negative totals (refunds) are supported; zero-weight parts

Input parameters:

- `currency` (string): ISO 4217 alphabetic code, upper case.
- `exponent` (integer): Override the ISO 4217 exponent; required for codes not on the list.
- `parts` (integer): Equal split into this many parts.
- `remainder` (string): largest-remainder (default): one unit at a time to the part with the largest rounding claim, ties to the lowest index. first / last: the whole residual to the first / last part with positive weight.
- `rounding` (string): Rounding of each share before the residual is moved. Default half-even. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: tow…
- `total` (string, required): Decimal string such as "-12.50" (up to 15 integer and 12 fraction digits). JSON numbers are not accepted: they are binary floats.
- `weights` (array): Non-negative decimal-string weights, e.g. ["1","1","2"] or percentages. Give weights or parts.

### `proration` (~162 tokens)

Proration and day-count fractions (30/360, ACT/365F, ACT/360, ACT/ACT ISDA) on half-open date ranges — Computes the year fraction of up to 100 half-open date ranges [start, end) under a named ISDA day-count convention, and optionally the prorated charge, for an agent billing a partial period or accruing interest. Conventions follow Section 4.16 of the 2006 ISDA Definitions: 30/360, 30E/360, 30E/360 (ISDA), Actual/365 (Fixed), Actual/360, Actual/Actual (ISDA), 1/1. `end` is the day immediately follo

Input parameters:

- `items` (array, required)

### `metered-price` (~338 tokens)

Tiered usage pricing: graduated or volume tiers, included quantity, package units, minimum charge — Prices a usage quantity against up to 50 tiers, graduated (each tier prices only its own units) or volume (the tier holding the whole quantity prices all of it), for an agent checking a usage bill or quoting a plan. Order of operations: subtract the included quantity, convert to billing packages (per N units, rounded up, down or not at all), price the tiers, add flat fees, apply the minimum charge

Input parameters:

- `currency` (string): ISO 4217 alphabetic code, upper case.
- `exponent` (integer)
- `included` (string): Free quantity subtracted before packaging and tiers (never below zero).
- `minimum` (string): Minimum charge in major units, applied after the tiers.
- `mode` (string, required)
- `packageRounding` (string): How a partial package is billed when per > 1. Default up.
- `per` (string): Units per billing package (default 1). Tiers are expressed in packages.
- `quantity` (string, required): Decimal string such as "-12.50" (up to 15 integer and 12 fraction digits). JSON numbers are not accepted: they are binary floats.
- `rounding` (string): Final rounding to the minor unit. Default half-up. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: toward zero. ceiling: to…
- `tiers` (array, required)

### `invoice-audit` (~285 tokens)

Invoice arithmetic audit: line extensions, discounts, supplied tax, totals, with the drift in minor units — Recomputes up to 500 invoice lines in exact decimal arithmetic and compares them with the stated amounts, for an agent about to approve, pay or reconcile an invoice. Checks: quantity x unit price less discount equals the line amount; tax is taken as supplied (tax amounts are summed, never looked up) and, where a rate is given, tax equals rate x line amount under the declared rounding scope (per li

Input parameters:

- `currency` (string): ISO 4217 alphabetic code, upper case.
- `exponent` (integer)
- `lines` (array, required)
- `rounding` (string): Default half-up. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: toward zero. ceiling: toward +infinity. floor: toward -inf…
- `stated` (object)
- `taxRounding` (string): line (default): each line's tax is rounded on its own. invoice: tax is rounded once per distinct rate on the sum of the line amounts, and compared with the supplied tax sum for that rate.
- `toleranceMinor` (integer): Largest absolute drift in minor units still treated as a match. Default 0.

### `price-change-attribution` (~309 tokens)

Attribute a total's change to quantity, price, FX, added and removed lines (sums exactly) — Explains why a total moved between two versions of a quote, order or invoice (up to 300 lines each), for an agent that must say how much of the change came from quantity, unit price, exchange rate, new lines and dropped lines. Lines are matched by key. Matched lines are decomposed by sequential substitution in the declared factor order (default quantity, then price, then fx), so the effects sum to

Input parameters:

- `after` (array, required)
- `before` (array, required)
- `currency` (string): ISO 4217 alphabetic code, upper case.
- `exponent` (integer)
- `fx` (object): Multiplier from line currency to reporting currency, before and after. Default 1 and 1.
- `order` (array): Substitution order of the factors; each at most once. Default [quantity, price, fx].
- `rounding` (string): Default half-even. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: toward zero. ceiling: toward +infinity. floor: toward -i…
- `statedAfterTotal` (string): Optional stated total of `after` to verify.
- `statedBeforeTotal` (string): Optional stated total of `before` (reporting currency) to verify.

### `locale-number` (~150 tokens)

Parse locale-formatted money text (1.234,56, 1,00,000, accounting parentheses) without guessing — Parses up to 100 number or money strings such as "1.234,56", "1,00,000", "(1,234.50)", "￥1,000" or "CHF 1'234.50" into canonical decimal strings, for an agent reading amounts from documents, emails or tables. With a BCP 47 locale it applies that locale's CLDR separators (read from Intl.NumberFormat); without one it lists every valid reading and an ambiguous string such as "1,234" returns unknown w

Input parameters:

- `items` (array, required)

### `number-to-words` (~132 tokens)

Number and cheque-amount words: English (US, UK, Indian lakh/crore) — Spells out a number or a money amount in English words for a cheque, contract or invoice, for an agent that must write the amount in words next to the figures. Locales: en-US ("one hundred twenty-three"), en-GB ("one hundred and twenty-three"), en-IN (lakh and crore, "one crore twenty lakh"). With a currency it returns the integer words, the minor-unit fraction as digits over 10^exponent ("56/100"

Input parameters:

- `items` (array, required)

### `id-kind` (~153 tokens)

Identify an identifier's kind: UUID version, ULID, KSUID, snowflake, Stripe/GitHub/AWS prefix, EVM address, email, E.164 — Classifies up to 100 identifier strings by format and, where it can be read, decodes the embedded timestamp, for an agent that must not pass an id of the wrong kind to a payment, ledger or API call. Recognises UUID (RFC 9562 version and variant, nil and max), ULID, KSUID, Discord and Twitter snowflakes, EIP-55 EVM addresses (checksum verified), email (WHATWG syntax and RFC 5321 length limits), E.1

Input parameters:

- `items` (array, required)

### `quote-normalize` (~184 tokens)

Normalise supplier quotes to one comparable unit price (currency, unit of measure, tax, discount) — Converts up to 200 quoted prices to a net price per base unit in one currency, for an agent comparing supplier quotes. Each line: price for `per` units of a unit of measure, optional tax-inclusive flag and rate, optional percentage discount, any currency. Uses only the caller's exchange rates and unit factors (1 uom = factor base units); a currency without a rate, a unit without a factor, or a tax

Input parameters:

- `baseUom` (string): Name of the base unit prices are normalised to (default "unit").
- `fxRates` (array)
- `lines` (array, required)
- `targetCurrency` (string, required): ISO 4217 alphabetic code, upper case.
- `uomFactors` (array)

### `pack-size` (~159 tokens)

Pack sizes, MOQ, order increments, overbuy cap and price breakpoints: what to actually order — Finds the cheapest valid order quantity for a requested number of units across up to 50 supplier options, for an agent buying parts or consumables sold in packs. Each option has a pack size (units per pack or notation such as "6x100", "case of 12", "12/case", "case of 6 inners"), an optional minimum order quantity, an order increment and price breakpoints; the order is rounded up to a multiple of

Input parameters:

- `options` (array, required)
- `overbuyCapPercent` (string): Reject orders exceeding the request by more than this percent.
- `requested` (integer, required): Units needed.

### `qualifier-compare` (~145 tokens)

Requested vs quoted specification attributes: met, not met or not comparable — Compares up to 200 requested attribute requirements with the values a supplier quoted (voltage, grade, finish, tolerance, brand, certification), for an agent checking that a quote matches the request before buying. Requirements are eq, ne, gte, lte, gt, lt, between (value..max), in (a list) or present; numeric comparisons use exact decimals, an optional tolerance, and the caller's unit conversions

Input parameters:

- `caseSensitive` (boolean)
- `conversions` (array): Caller-supplied unit conversions; none are built in.
- `items` (array, required)

### `bid-coverage` (~127 tokens)

Bid coverage: uncovered lines, substitutions, partial quantities and conditional bundles — Checks which required lines of a tender or RFQ are covered by the bids received (up to 200 lines, 30 bidders, 2000 offers), for an agent comparing responses. A line is covered when firm offers (exact item, no condition, no bundle) sum to the required quantity; substitute offers, offers bound to a bundle (all-or-nothing across the lines in that bundle) and offers with a stated condition are reporte

Input parameters:

- `bids` (array, required)
- `lines` (array, required)

### `coa-gate` (~147 tokens)

Certificate of analysis vs specification: pass, fail or indeterminate per clause — Checks the values on a certificate of analysis or test report against specification limits clause by clause (up to 200 clauses), for an agent accepting a lot or a supplier's material. Each clause has a parameter, an optional min and max and a unit; each result has a value, an optional reported uncertainty and an optional less-than or greater-than qualifier ("<0.01"). rule simple (default): the rep

Input parameters:

- `clauses` (array, required)
- `conversions` (array): Caller-supplied unit conversions; none are built in.
- `results` (array, required)
- `rule` (string)

### `calibration-coverage` (~129 tokens)

Calibration certificate vs intended use: range, uncertainty and validity — Checks whether an instrument's calibration certificate covers an intended measurement, for an agent about to rely on a reading or accept a calibrated device. Three checks: the intended range [min, max] lies inside the calibrated ranges (touching or overlapping ranges are joined); the stated expanded uncertainty of every calibrated range used is no larger than the required uncertainty; the calibrat

Input parameters:

- `asOf` (string, required): The reference date for validity; required, never defaulted to today.
- `certificate` (object, required)
- `use` (object, required)

### `business-deadline` (~517 tokens)

Business-day deadline (clear days, cutoffs, DST) on a named or caller calendar — Computes the date (and optionally the instant) a business-day deadline falls on, for an agent drafting or checking a contract, notice, SLA or partner response window: '10 clear business days' (both endpoints excluded) or 'within 10 business days' (end day counted), forward or backward, with an after-cutoff roll, caller or named holiday calendar and a DST-aware deadline time. Named calendars (US fe

Input parameters:

- `calendar` (string, required): Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list).
- `claimedDeadline` (string): A deadline date someone asserted; the check fails with the computed date if it differs.
- `counting` (string, required): clear: days strictly between start and deadline, so the deadline is business day N+1. elapsed: the deadline is business day N after start (the end day is counted).
- `cutoff` (string): Local HH:MM. With a date-time start (direction after), a start strictly later than the cutoff, or on a non-business day, is deemed received on the next business day. 17:00 exactly is on time. Without…
- `days` (integer, required)
- `deadlineTime` (string): Local HH:MM at which the deadline expires on the deadline date; needs timeZone to produce an instant.
- `direction` (string): Default after. before counts backward from start (for 'at least N days before the hearing').
- `disambiguation` (string): How to read a deadline time that falls in a DST gap (earlier: before-gap offset reading backward; later: shifted forward) or overlap (earlier/later occurrence). Without it, a gap or overlap returns u…
- `holidays` (array): Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
- `start` (string, required): Local date YYYY-MM-DD, or local date-time YYYY-MM-DDTHH:MM[:SS] (the notice/receipt moment). Never read from the clock.
- `timeZone` (string): IANA zone for deadlineTime.
- `weekend` (array): Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.

### `dst-check` (~130 tokens)

DST gap and overlap check for local times and stated offsets in an IANA zone — Checks up to 100 local date-times (YYYY-MM-DDTHH:MM) or offset timestamps against an IANA time zone and reports whether each wall time exists once, never (spring-forward gap) or twice (fall-back overlap), with every real instant and the offset in force; also lists a zone's offset transitions in a year. Built for an agent scheduling a meeting, cron job or deadline in someone else's zone. Uses the r

Input parameters:

- `items` (array, required)
- `transitionsIn` (object)

### `date-claim-check` (~147 tokens)

Does this date fall on the claimed weekday? (batch, year boundaries and leap days) — Checks up to 200 claims 'Monday 2026-12-28' against the proleptic Gregorian calendar and reports the real weekday, whether the date exists (2026-02-29 does not), and the nearest date carrying the claimed weekday; a claim 'Friday, 13 March' without a year returns the years in a range where it holds. Built for an agent verifying dates in a document, email or itinerary. Gregorian only (no Julian date

Input parameters:

- `fromYear` (integer)
- `items` (array, required)
- `toYear` (integer)

### `week-number` (~217 tokens)

Week number and week-year for dates under ISO 8601, US or custom rules (53-week years) — Returns the week number, week-year, number of weeks in that year and the week's first and last day for up to 200 dates under ISO 8601 (Monday start, week 1 holds 4 January), the US convention (Sunday start, week 1 holds 1 January) or a custom weekStart/minimalDays rule, and checks an asserted week or week-year (2027-01-01 is ISO 2026-W53). Built for an agent reading or writing week-based dates in

Input parameters:

- `items` (array, required)
- `minimalDays` (integer): Days of the new year the first week must contain (custom).
- `system` (string, required): iso: weekStart Monday, minimalDays 4. us: weekStart Sunday, minimalDays 1. custom: give weekStart and minimalDays.
- `weekStart` (integer): 0=Sunday..6=Saturday (custom).

### `market-session` (~304 tokens)

Is the exchange in its core session at this instant? (NYSE holidays and 13:00 early closes, or a caller calendar) — For up to 50 caller-supplied instants, reports whether the NYSE core session (09:30-16:00 America/New_York, 13:00 on early-close days) is open, the reason when closed (weekend, named holiday, before open, after close), that day's open and close instants and the next open; or the same for a caller venue (zone, open, close, holidays, early closes). NYSE data is a dated snapshot of nyse.com covering

Input parameters:

- `close` (string): venue caller only, local HH:MM, after open.
- `earlyCloses` (array): venue caller only.
- `expect` (string): If given, status is fail for any instant whose state differs.
- `holidays` (array): Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
- `instants` (array, required): RFC 3339 timestamps with Z or offset.
- `open` (string): venue caller only, local HH:MM.
- `timeZone` (string): venue caller only.
- `venue` (string, required)
- `weekend` (array): Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.

### `settlement-date` (~313 tokens)

Settlement date for a trade date: US equities T+1 on NYSE and Federal Reserve days, or T+n on a caller calendar — Computes the settlement date for a trade date under US equities T+1 (17 CFR 240.15c6-1, compliance date 2024-05-28) counting only days when the NYSE and the Federal Reserve Banks are open, or T+n on a named or caller calendar, and checks an asserted settlement date. The settlement-day rule (NYSE and Reserve Banks both open, so Columbus Day and Veterans Day are skipped) is our inference, not a publ

Input parameters:

- `calendar` (string): Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list).
- `claimedSettlementDate` (string)
- `cycleDays` (integer): custom only.
- `holidays` (array): Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
- `settlement` (string, required): us-equities: T+1 since 2024-05-28 on the us-equities-settlement calendar (2026-2028). custom: cycleDays on calendar/holidays/weekend.
- `tradeDate` (string, required)
- `weekend` (array): Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.

### `calendar-convert` (~257 tokens)

Convert dates between Gregorian and Hijri (named variants), Hebrew, Persian, Ethiopian; Western and Orthodox Easter — Converts a Gregorian date (or a Hebrew, Persian, Ethiopian or Hijri date) to the other calendars via the runtime's ICU, always naming the Hijri variant (Umm al-Qura, tabular civil, tabular astronomical-epoch, ICU astronomical) and flagging when variants disagree on the day; with mode easter, returns Western (Gregorian computus) and Orthodox (Julian computus, with its Gregorian equivalent) Easter a

Input parameters:

- `date` (string): convert: Gregorian date. Exactly one of date or from.
- `feasts` (boolean): easter: also list Ash Wednesday, Good Friday, Ascension, Pentecost and other moveable feasts.
- `from` (object)
- `mode` (string, required)
- `to` (array): Calendars to convert into; hijri-all returns Umm al-Qura, tabular civil and ICU astronomical (add islamic-tbla explicitly; it differs from civil by its epoch) and fails when they disagree. Default: a…
- `years` (array): easter: Gregorian years.

### `fiscal-period` (~345 tokens)

Fiscal year, quarter and period for a date: month-aligned or 52/53-week (4-4-5, 4-5-4, 5-4-4) calendars — Maps up to 100 dates to a fiscal year, quarter, period and week for a caller-defined fiscal calendar: a month-aligned year (starts on day 1 of a named month) or a 52/53-week year ending on a given weekday last in or closest to a month end, in a 4-4-5, 4-5-4 or 5-4-4 pattern with the 53rd week appended to the final period; detects 53-week years and checks an asserted fiscal year, quarter or period.

Input parameters:

- `endMonth` (integer): 52-53-week: month near whose end the year ends.
- `endRule` (string): 52-53-week: last endWeekday in endMonth, or the endWeekday closest to endMonth's last day.
- `endWeekday` (integer): 52-53-week: weekday the year ends on, 0=Sunday.
- `items` (array, required)
- `pattern` (string): 52-53-week: weeks per period within each quarter.
- `startMonth` (integer): month-aligned: month in which the fiscal year starts, on day 1.
- `type` (string, required)
- `yearLabel` (string, required): start: the fiscal year is named for the calendar year it begins in. end: for the calendar year it ends in (US federal FY2027 begins 2026-10-01).

### `naive-timestamp-hazard` (~160 tokens)

Which timestamps are anchored? Flags naive local times, zone abbreviations, date-only, epoch units and d/m ambiguity — Classifies up to 200 timestamp strings as anchored (RFC 3339 with Z or offset), naive local (no offset), date-only, epoch seconds or milliseconds, zone abbreviation, ambiguous numeric date, or unparseable, and lists the hazard of each; with assumedTimeZone it also reports whether a naive time falls in a DST gap or overlap there, every instant it could mean, and offsets that contradict the zone. Bu

Input parameters:

- `assumedTimeZone` (string): IANA zone the producer is believed to use; used for gap/overlap and offset-consistency checks.
- `timestamps` (array, required)

### `time-bucket-check` (~193 tokens)

DST hazards for hourly and daily buckets in a zone: skipped hours, repeated hours, 23- and 25-hour days — For a time zone and a date range of up to 1100 days, lists every offset transition and what it does to local bucketing: the hourly labels that never occur (spring-forward), the hourly labels that occur twice and would merge two real hours when grouped by local time (fall-back), and the 23-, 24.5- or 25-hour days; optionally checks up to 500 caller hourly labels (YYYY-MM-DDTHH:00) for non-existent

Input parameters:

- `from` (string, required): First local date, inclusive.
- `labels` (array): Local hour labels to check, e.g. 2026-03-08T02:00.
- `timeZone` (string, required)
- `to` (string, required): Last local date, inclusive.

### `recurrence-expand` (~435 tokens)

Expand an RRULE or 5-field cron into concrete occurrences with DST handling, exclusions and conflict detection — Expands an RFC 5545 RRULE (FREQ DAILY/WEEKLY/MONTHLY/YEARLY, INTERVAL, COUNT, UNTIL, BYDAY with ordinals, BYMONTHDAY, BYMONTH, BYSETPOS, WKST; DTSTART with TZID; EXDATE) or a crontab(5) expression into up to 366 occurrences in a time zone, with the UTC instant of each, DST gap or overlap flags, caller blackout dates, a plain-English reading, and optionally the occurrences where it collides with a

Input parameters:

- `blackouts` (array): Inclusive local date ranges to drop (holidays, freezes).
- `dtstart` (string): Local DTSTART when the rule text has none.
- `durationMinutes` (integer): Occurrence length, for conflict overlap.
- `exdates` (array): Extra excluded local date-times (YYYY-MM-DDTHH:MM[:SS]) or dates (YYYY-MM-DD, excludes that day).
- `from` (string): Local start of the output window; required for cron, default DTSTART for rrule.
- `kind` (string, required)
- `limit` (integer): Maximum occurrences returned (default 20).
- `other` (object): A second rule to compare; conflicts are occurrences whose intervals overlap (equal instants when both durations are 0).
- `rule` (string, required): rrule: 'DTSTART;TZID=America/New_York:19970902T090000\nRRULE:FREQ=DAILY;COUNT=10\nEXDATE;TZID=America/New_York:19970903T090000' or just 'FREQ=...' with dtstart. cron: '*/15 9-17 * * 1-5' (dom and dow…
- `timeZone` (string): IANA zone for local times (required for cron; for rrule unless DTSTART has TZID or Z).
- `to` (string): Local end of the window, inclusive.

### `slot-intersect` (~142 tokens)

Common free time across participants: intersect availability windows, report who blocks — Intersects up to 20 participants' free windows (up to 200 each, half-open RFC 3339 intervals with Z or offsets, so mixed time zones are fine) into the common slots at least minMinutes long, optionally clipped to a search window; when nothing fits, names the participants whose removal would create a slot. Built for an agent scheduling a meeting from already-fetched availability. It does not read ca

Input parameters:

- `minMinutes` (integer): Minimum slot length; default 1.
- `participants` (array, required)
- `window` (object): Only consider this range.

### `appointment-fit` (~277 tokens)

Does this appointment fit: opening hours in the venue's zone, closed days, existing bookings with buffers, minimum notice — Checks one proposed appointment (instant + duration) against a venue's local opening hours per weekday, closed dates or a named holiday calendar, up to 500 existing bookings with a buffer on each side, and a minimum notice measured from a caller-supplied asOf; every violated rule is returned as a witness with the conflicting booking or hour block. Local hours are resolved in the venue's IANA zone

Input parameters:

- `asOf` (string): Reference instant for minimum notice.
- `bookings` (array)
- `bufferMinutes` (integer): Required gap on each side of the appointment.
- `calendar` (string): Optional named holiday calendar for closed days (unsupported outside its range). Without it only holidays/weekend you list apply; hours decide the weekdays.
- `durationMinutes` (integer, required)
- `holidays` (array): Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
- `hours` (array, required)
- `minNoticeMinutes` (integer): Needs asOf.
- `start` (string, required)
- `timeZone` (string, required): Venue zone in which hours apply.
- `weekend` (array): Ignored for hours; with a named calendar only its holidays are used.

### `temporal-constraints` (~158 tokens)

Are these timing constraints satisfiable? Earliest/latest time per event, or the conflicting constraints — Solves a simple temporal network: up to 40 named time points, up to 200 difference constraints 'b is between min and max minutes after a' and optional fixed instants, relative to a caller origin instant. When consistent it returns each point's earliest and latest feasible instant (where bounded); when not, it returns the cycle of constraints that contradict each other, with the total impossible sl

Input parameters:

- `constraints` (array, required)
- `fixed` (array)
- `origin` (string, required): Instant that point 'origin' (an implicit extra point) is at; all minutes are relative to it.
- `points` (array, required)

### `shelf-life-check` (~137 tokens)

Is this lot still within shelf life on a given date? (unopened and after-opening limits, minimum remaining days) — For up to 100 lots, computes the expiry date from manufacture/fill date + shelf life (days, weeks, months, years; month arithmetic clamps to month end) and from opened date + after-opening life, takes the earlier, and checks it against a caller asOf date and an optional minimum remaining days at receipt; flags a labelled expiry that disagrees with the computed one. The last day of life is the expi

Input parameters:

- `asOf` (string, required)
- `items` (array, required)

### `credential-coverage` (~169 tokens)

Do licences, certificates or insurance policies cover a required period without gaps? — Given a required date range (a contract term, a project, a shipment window) and up to 200 credentials each valid from a date to a date (both inclusive), reports the merged covered ranges, every uncovered gap with its first and last day and length, and whether each checkpoint date is covered; a credential ending the day before the next starts is contiguous. Built for an agent verifying insurance, l

Input parameters:

- `checkpoints` (array): Specific dates that must be covered (delivery date, audit date).
- `credentials` (array, required)
- `required` (object, required)
- `toleratedGapDays` (integer): Gaps up to this many days are reported but do not fail (a grace period you are entitled to).

### `storage-charge-clock` (~397 tokens)

Storage, demurrage or detention charge: free-time end date, chargeable days and tiered amount — Counts days between a received date and a released date for storage, demurrage, detention or parking charges: you state whether the receipt day and the release day count, how free days are counted (calendar or business days on a named or caller calendar), and a tiered per-day rate schedule by chargeable day number; returns the last free day, chargeable days, a per-tier breakdown and the total in m

Input parameters:

- `calendar` (string): Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list).
- `chargeCounting` (string, required): Whether chargeable days skip weekends/holidays.
- `claimedChargeMinor` (integer)
- `currency` (string, required): ISO 4217 code in capitals, e.g. USD. rateMinor is in this currency's minor units (cents for USD).
- `freeCounting` (string, required): Whether free days skip weekends/holidays; business needs calendar.
- `freeDays` (integer, required): Free days before charges start; 0 for none.
- `holidays` (array): Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
- `receiptDayCounts` (boolean, required): Whether the day of receipt is day 1.
- `receivedOn` (string, required): Date the goods or container were received, YYYY-MM-DD.
- `releaseDayCounts` (boolean, required): Whether the release day is counted.
- `releasedOn` (string, required): Date released, YYYY-MM-DD; not before receivedOn.
- `tiers` (array, required)
- `weekend` (array): Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.

### `booking-change-penalty` (~222 tokens)

Which cancellation or change tier applies at this moment, and what does it cost? — Given a booking start, the moment of change, the booking amount and a tiered policy whose deadlines are either elapsed hours before start ('48 hours') or local calendar days at a local time ('18:00 the day before' in the venue's zone, DST-correct), returns the applicable tier, its deadline instants, the penalty in minor units under your stated rounding, and when the next tier begins; checks an ass

Input parameters:

- `amountMinor` (integer, required)
- `changeAt` (string, required): The moment of cancellation/change; never read from the clock.
- `claimedPenaltyMinor` (integer)
- `currency` (string, required)
- `noShowTier` (string): Tier name charged when changeAt is after startAt; default the most severe tier.
- `rounding` (string, required): Applied to percentage penalties.
- `startAt` (string, required)
- `tiers` (array, required)
- `timeZone` (string): Needed for daysBefore tiers.

### `age-threshold` (~189 tokens)

Age in complete years on a date and the exact dates a minimum or maximum age is reached (leap-day births) — For up to 100 people, computes age in complete years and months on a caller asOf date, the date they reach each minimum age (the birthday) and the first day they exceed each maximum age, and checks min/max age requirements; 29 February births need a declared common-year rule (28 February or 1 March) because jurisdictions differ. Built for an agent checking eligibility (18+, under 65, 21 to buy). I

Input parameters:

- `asOf` (string, required)
- `items` (array, required)
- `leapDayRule` (string): In common years a 29 February birthday is observed on 28 February or on 1 March depending on the legal context you apply; you must choose. Required if any birth date is 29 February.

### `cron-explain` (~264 tokens)

Cron parse, humanize and next N runs — Parses a POSIX 5-field or Quartz 6/7-field cron expression (plus macros @yearly/@monthly/@weekly/@daily/@hourly), returns a plain-English summary and the next N scheduled runs in a given IANA timezone, and reports if the expression never fires or lands on a DST-ambiguous wall-clock. Handles step syntax, named months and days, Quartz '?'/L/W/# extensions, and the POSIX dom-OR-dow rule when both fie

Input parameters:

- `after` (string): ISO-8601 instant: find runs strictly after this. Defaults to 1970-01-01T00:00:00Z.
- `count` (integer): How many future runs to return, 1-50. Default 5.
- `expression` (string, required): The cron expression or macro, e.g. '*/15 9-17 * * 1-5' or '@weekly'.
- `flavor` (string): Which cron dialect. Defaults to posix (5 fields) or quartz (6/7 fields) based on token count.
- `timezone` (string): IANA timezone name, e.g. 'America/Los_Angeles'. Defaults to UTC.

### `checksum` (~143 tokens)

Identifier check digits: IBAN, ISBN, GTIN, VIN, ISIN, LEI and more, in a batch — Validates the format and check digit of up to 100 identifiers per call, for an agent about to put an IBAN, ISBN, GTIN/EAN/UPC, container number, VIN, ISIN, CUSIP, SEDOL, LEI, IMO number, BIC or Luhn number into a payment, order or record. Each item is {kind, value}; with kind omitted the engine proposes candidate kinds and answers unknown if two kinds both validate. Reports the normalized form (lo

Input parameters:

- `items` (array, required)

### `vin-decode` (~128 tokens)

VIN decode: manufacturer (WMI), model year, check digit — Decodes up to 50 VINs per call for an agent handling a vehicle listing, claim or order: validates the 17 characters and letters I/O/Q, the position-9 check digit (49 CFR 565.15), the world manufacturer identifier from a bundled NHTSA vPIC snapshot, and the model year from position 10. Position 10 repeats every 30 years: pass vehicleClass light (position 7 resolves the century) or asOf, otherwise b

Input parameters:

- `items` (array, required)

### `gtin-hierarchy` (~139 tokens)

GTIN hierarchy: GTIN-8/12/13/14 forms, GS1 prefix, packaging-level link — Takes up to 100 GTINs and, for an agent reconciling a product feed or order lines, validates each check digit, converts it to the 14-digit form, reads the indicator digit and GS1 Prefix (restricted-circulation, ISBN/ISSN range, coupon), and, when a parent GTIN is given, checks the two share one base item (the packaging-level link). It does not look up the brand owner, the product or the country of

Input parameters:

- `items` (array, required)

### `platform-text-fit` (~136 tokens)

Does this text fit: SMS segments, X posts, store listings, ad and push limits — Checks up to 50 texts per call against a platform limit, for an agent writing a message, post, store listing, ad or push payload that must not be truncated or split. sms: GSM 7 bit vs UCS-2 and the exact segment boundaries per 3GPP TS 23.038 (extension characters cost 2 septets and never straddle a segment; an emoji is 2 UTF-16 units). x: weighted length per the open-source twitter-text config v3

Input parameters:

- `items` (array, required)

### `tax-id-format` (~120 tokens)

VAT / tax-id format and check digit (AT, BE, DE, DK, FI) — Checks the structure and check digit of up to 100 EU VAT numbers per call (Austria, Belgium, Germany, Denmark, Finland), for an agent about to put a supplier or customer VAT number on an invoice or into a record. Every other country answers unsupported rather than guessing a pattern. It never says whether the number is registered or active (that needs VIES or the national register), and a pass is

Input parameters:

- `items` (array, required)

### `timecode-convert` (~203 tokens)

SMPTE timecode conversion: drop-frame and non-drop, frames, exact seconds — Converts up to 200 timecodes, frame counts or times between SMPTE HH:MM:SS:FF (non-drop), HH:MM:SS;FF (drop-frame, 29.97 and 59.94), frame numbers and exact rational seconds, for an agent editing video, captions or logs at a stated frame rate. Rates are integers, a rational like 30000/1001, or the named 23.976, 29.97, 59.94, 119.88; any other decimal is rejected, never rounded. Integer arithmetic

Input parameters:

- `items` (array, required)
- `rate` (string, required): 24, 25, 30, 50, 60, 24000/1001, or the names 23.976, 29.97, 59.94, 119.88.

### `subtitle-lint` (~246 tokens)

Subtitle lint: SRT and WebVTT overlaps, duration, reading speed, line length — Parses an SRT or WebVTT file (up to 400000 characters, 4000 cues) and checks every cue for an agent about to deliver or burn in captions: end after start, overlaps and out-of-order cues, minimum gap, minimum and maximum duration, lines per cue, characters per line and characters per second (markup tags are not counted). Rules come from a named profile (netflix-en-adult, netflix-en-children, values

Input parameters:

- `custom` (object): Your own rules; these override profile values.
- `format` (string): Default: vtt if the text starts with WEBVTT, else srt.
- `frameRate` (number): Needed to turn a minimum gap in frames into milliseconds.
- `profile` (string): netflix-en-adult: 42 chars/line, 2 lines, 20 cps, 5/6 s to 7 s, 2-frame gap. netflix-en-children: same at 17 cps.
- `text` (string, required): The whole .srt or .vtt file.

### `pronunciation-apply` (~174 tokens)

Pronunciation lexicon to SSML phoneme and sub tags — Applies your pronunciation lexicon (up to 200 terms, each an IPA string or a spoken alias) to a text of up to 20000 characters and returns SSML 1.1 with <phoneme alphabet="ipa"> or <sub alias> around each whole-word match, XML-escaped, for an agent preparing text for a text-to-speech engine. Matching is whole-word, longest term first, left to right, deterministic. It does not guess pronunciations,

Input parameters:

- `lang` (string): xml:lang of the speak element (default en-US).
- `lexicon` (array, required)
- `text` (string, required)
- `wrapSpeak` (boolean): Wrap in <speak version="1.1"> (default true).

### `speech-normalize` (~162 tokens)

Normalize numbers, currency, phone numbers and units for text-to-speech — Rewrites digits in up to 20000 characters of text into spoken words for a TTS engine, for locales en-US and en-GB: cardinals, ordinals, years (with a preceding cue such as "in" or a month) and decades, decimals, percentages, currency with ISO 4217 minor units ("$12.50" -> "twelve dollars and fifty cents"), phone numbers read digit by digit, and SI/common units with locale spelling (meter/metre). O

Input parameters:

- `locale` (string): BCP 47 tag. en-US (default) and en-GB are supported; anything else returns unsupported.
- `text` (string, required)

### `font-coverage` (~203 tokens)

Font coverage: does this font have glyphs for this text, and does it fit the box — Reads a TrueType or OpenType font you supply as base64 (up to 2 MB) and a text of up to 5000 characters, for an agent about to render text in a fixed font: lists every code point with no glyph in the cmap (formats 4 and 12) and sums the hmtx advance widths to test a width in pixels. Every offset is bounds-checked. It does not apply kerning, ligatures or shaping (combining marks and complex scripts

Input parameters:

- `fontBase64` (string, required): Base64 of a .ttf or .otf file (sfnt, not WOFF).
- `fontSizePx` (number): Needed for a width check.
- `maxWidthPx` (number): Box width; the widest line (split on \n) must fit.
- `text` (string, required)

### `font-convert` (~194 tokens)

Font converter: TTF/OTF, WOFF and WOFF2 containers, with the font's own embedding permission checked — Repackages a font you supply as base64 (up to 2 MB) between the sfnt (.ttf/.otf), WOFF and WOFF2 containers, for an agent or build step that needs a web font in a particular format: every table is carried over unchanged, the result is read back and its table digest compared with the source, and the font's own OS/2 embedding bits are checked first (a restricted font fails and nothing is returned).

Input parameters:

- `fontBase64` (string, required): Base64 of a .ttf, .otf, .woff or .woff2 file (not a .ttc collection), up to 2 MB.
- `to` (string, required): Target container. sfnt is the plain .ttf/.otf file.

### `font-face-css` (~248 tokens)

@font-face block generated from the font file: family, weight, style, stretch and unicode-range read from the font — Reads a font you supply as base64 (up to 2 MB, any of TTF, OTF, WOFF, WOFF2) and writes an @font-face rule for the URLs you will serve it from, for an agent or build step generating CSS: font-family from the name table, font-weight from OS/2 (or the fvar wght range of a variable font), font-style, font-stretch, and unicode-range from the cmap. Names and URLs are escaped as CSS strings. It does not

Input parameters:

- `family` (string): Overrides the family name read from the font.
- `fontBase64` (string, required): Base64 of a .ttf, .otf, .woff or .woff2 file (not a .ttc collection), up to 2 MB.
- `fontDisplay` (string): Default swap.
- `includeUnicodeRange` (boolean): Default true; omitted automatically for fonts with more than 300 cmap ranges.
- `sources` (array, required): One entry per file you serve, best format first.

### `font-glyph-svg` (~201 tokens)

Font to SVG: a line of text drawn as SVG paths from the font's own TrueType outlines — Reads a TrueType-outline font you supply as base64 (up to 2 MB; TTF, WOFF or WOFF2) and returns up to 200 characters of single-line text as an SVG made of <path> outlines (one per distinct glyph, placed with <use>), plus each glyph's path data in font units (y up), for an agent producing a logo, icon label or image that must not depend on the font being installed. Composite glyphs and their transf

Input parameters:

- `fontBase64` (string, required): Base64 of a .ttf, .otf, .woff or .woff2 file (not a .ttc collection), up to 2 MB.
- `fontSizePx` (number): Default 100.
- `text` (string, required): One line; line breaks are not laid out.

### `x509-inspect` (~239 tokens)

X.509 certificate inspection from PEM — Takes a PEM-encoded X.509 certificate and returns its fields (subject, issuer, serial, validity window, SANs, key usage, EKU, basic constraints, signature algorithm, public key algorithm and bit size) plus a fail-on-issue audit: expired or not-yet-valid, hostname/SAN mismatch per RFC 6125 §6.4.3 wildcards, weak signature (SHA-1), short RSA (<2048), serverAuth without SAN (CABF BR 7.1.4.2.1). Decod

Input parameters:

- `hostname` (string): Optional hostname to check against the certificate's SANs.
- `intermediates` (array): Intermediate certs (PEM) between leaf and anchor.
- `maxChainDepth` (integer): Chain depth cap (default 8).
- `nowIso` (string): Override 'now' for deterministic tests.
- `pem` (string, required): A PEM block beginning with '-----BEGIN CERTIFICATE-----'.
- `trustAnchors` (array): Trust anchors (PEM). When present, chain cryptographic verification runs.

### `unit-convert` (~151 tokens)

Exact unit conversion with dimensional analysis (NIST SP 811) — Converts up to 100 values between units for an agent that needs the exact factor and a refusal when the units do not match: SI and NIST SP 811 length, mass, time, volume, pressure, energy, power, temperature, with compound expressions like kg*m/s^2. Rejects incompatible dimensions, converts absolute temperatures affinely through kelvin and temperature differences linearly, and converts mass to vol

Input parameters:

- `density` (object): Default density for items that cross mass and volume.
- `items` (array, required): Conversions to run.
- `precision` (integer): Significant digits of the reported value. Default 12.

### `recipe-scale` (~210 tokens)

Recipe scaling with caller-declared non-linear rules — Scales up to 60 ingredient quantities by a servings ratio or a factor for an agent resizing a recipe or batch formula, applying per-ingredient rules the caller declares: linear (the labelled default), power exponent, fixed amounts, min/max clamps and rounding steps, with an optional display unit via unit-convert. Reports what rounding did (relative drift, rounds-to-zero). It does NOT know which in

Input parameters:

- `density` (object): Default density for displayUnit conversions that cross mass and volume.
- `factor` (number): Scale factor, instead of fromServings/toServings.
- `fromServings` (number): Servings the recipe is written for.
- `ingredients` (array, required): Ingredients with quantity, unit and optional scaling rule.
- `maxRelativeDrift` (number): Fail an ingredient when rounding moves it by more than this fraction (0.1 = 10%).
- `toServings` (number): Servings wanted.

### `allergen-flag` (~266 tokens)

Allergen flags in an ingredient list (EU Annex II, US FALCPA + FASTER Act) — Scans an ingredient list for terms tied to the 14 allergens of EU Regulation 1169/2011 Annex II and the 9 US major food allergens (FALCPA plus sesame under the FASTER Act), for an agent or buyer checking a label or recipe. Returns each matched span with its character offsets, the allergen, the regime that lists it, and whether it sits in a 'may contain' clause. Pass the allergens a label declares

Input parameters:

- `declared` (array): Allergen keys the label declares. Any detected, non-precautionary allergen missing from this list fails. For jurisdictions=eu, wheat and gluten-cereal cover each other (one Annex II entry).
- `extraTerms` (array): Caller synonyms (for example a brand's own ingredient name), matched as literal words.
- `ingredients` (string, required): Ingredient list or label text, at most 20000 characters.
- `jurisdictions` (string): Which list(s) to apply. Default both. EU adds celery, mustard, lupin, molluscs, sulphites and gluten cereals (rye, barley, oats); the US list has no such entries.

### `formula-weight` (~296 tokens)

Formula weight from a chemical formula (Hill notation, IUPAC/CIAAW weights) — Parses a chemical formula (parentheses, brackets, hydrate dots such as CuSO4·5H2O, an ignored charge) for a chemist or an agent that must check a molar mass, and returns the Hill-notation formula, the formula weight in g/mol from the CIAAW abridged standard atomic weights summed exactly in decimal arithmetic, and mass fractions. Pass claimedWeight and tolerance to check a stated molar mass. Elemen

Input parameters:

- `claimedWeight` (number): Stated molar mass to check, g/mol.
- `elementWeights` (array): Caller-chosen weights; they take precedence over the table and are the only way to weigh elements without a standard atomic weight.
- `formula` (string): Chemical formula, at most 200 characters. Element symbols are case-sensitive (Co is cobalt, CO is carbon monoxide). Hydrate separators: . · • *. A trailing charge such as ^2+, 2- after a bracket, or…
- `mode` (string): formula (default) computes the weight; smiles validates syntax only.
- `smiles` (string): A single SMILES string without a name, at most 200 characters (mode smiles).
- `tolerance` (number): Allowed absolute difference from claimedWeight in g/mol. Default 0.01.

### `contrast-fix` (~342 tokens)

WCAG 2.2 contrast check with the minimal OKLCH lightness fix and colour-blind pair check — Checks up to 50 foreground/background hex pairs against a WCAG 2.2 contrast threshold (4.5 AA text, 3 large text and UI, 7 AAA, or your own) on the unrounded ratio, so 4.499 fails and exactly 4.5 passes, and for a failing pair returns the closest colour by OKLCH lightness (chroma and hue held, gamut-clipped, 8-bit) that meets it. Optionally simulates protanomaly, deuteranomaly and tritanomaly (Mac

Input parameters:

- `cvdMinDeltaE` (number): Smallest OKLab distance counted as distinguishable (default 0.05, a heuristic, not a standard).
- `cvdSeverity` (number): Enables the colour-vision-deficiency check at this severity, 0 to 1 (1.0 is dichromacy); between the published 0.1 steps the matrices are interpolated.
- `fixTarget` (string): Which colour to move for a failing pair (default foreground); none skips the fix.
- `level` (string): aa-normal 4.5 (default), aa-large 3, aaa-normal 7, aaa-large 4.5, non-text 3 (WCAG 2.2 SC 1.4.3, 1.4.6, 1.4.11).
- `pairs` (array, required): Foreground/background pairs.
- `threshold` (number): Overrides level: the minimum contrast ratio.

### `exposure-calc` (~204 tokens)

Photographic exposure value: solve aperture, shutter, ISO or EV, with equivalent exposures — Given any three of aperture (f-number), shutter time in seconds, ISO and scene EV at ISO 100, solves the fourth from EV = log2(N^2/t) and EV_S = EV_100 + log2(S/100), names the nearest one-third-stop f-number, and lists the equivalent shutter time at each f-number from f/1 to f/32. Given all four, checks that they agree within a tolerance in stops. Built for camera, lighting and image-generation a

Input parameters:

- `aperture` (number): f-number N.
- `ev100` (number): Scene light as exposure value at ISO 100.
- `iso` (number): ISO speed S.
- `shutterSeconds` (number): Exposure time t in seconds.
- `toleranceStops` (number): When all four are given: largest EV100 disagreement accepted (default 0.05).

### `print-estimate` (~339 tokens)

Print resolution, bleed and uncompressed bitmap size arithmetic — Given an image's pixel size and a print size (inches, millimetres or centimetres) plus optional bleed, margin and target ppi, returns the effective ppi over trim plus bleed, whether it meets the target, the pixel count a target ppi needs, the largest print size a target ppi allows, the safe area, and the exact uncompressed bitmap size. Built for print-on-demand, layout and image-prep agents; the t

Input parameters:

- `bitsPerChannel` (integer): Bits per channel (default 8).
- `bleed` (number): Bleed added on each side of the trim, in unit (default 0).
- `channels` (integer): Channels per pixel for the raw size (default 3).
- `claimedEffectivePpi` (number): An effective ppi you assert; checked against the computed value.
- `claimedRawBytes` (integer): An uncompressed byte count you assert.
- `heightPx` (integer, required): Image height in pixels.
- `margin` (number): Safe margin inside the trim on each side, in unit (default 0).
- `ppiTolerance` (number): Accepted ppi difference for claimedEffectivePpi (default 0.5).
- `printHeight` (number): Trim height in unit.
- `printWidth` (number): Trim width in unit.
- `targetPpi` (number): The resolution you require, in pixels per inch.
- `unit` (string): Unit for print size, bleed and margin (default in).
- `widthPx` (integer, required): Image width in pixels.

### `solar-position` (~237 tokens)

Sun position, sunrise and sunset for a place and instant (NOAA equations) — Computes sun elevation, azimuth, declination, equation of time, sunrise, solar noon and sunset (UTC) for a latitude/longitude and up to 100 caller-supplied instants using the NOAA Global Monitoring Laboratory solar calculator equations (Meeus). Polar day and polar night return sunrise and sunset as null with a reason, not an error. Reads no clock: every instant comes from the caller. Does not mode

Input parameters:

- `asOf` (string, required): ISO 8601 instant with Z or numeric offset; the call never reads the clock.
- `claim` (object): Optional claim about the asOf instant to check; tolerances default to 0.5 deg and 2 minutes.
- `instants` (array): Further instants, same place.
- `latitude` (number, required): Degrees north, -90 to 90.
- `longitude` (number, required): Degrees east, -180 to 180.
- `utcOffsetMinutes` (integer): Offset from UTC used to define the local calendar day for sunrise/sunset (default 0).

### `geo-distance` (~158 tokens)

Great-circle and WGS-84 ellipsoidal distance between coordinates — Computes the haversine (IUGG mean-radius sphere) and Vincenty inverse (WGS-84 ellipsoid) distance in metres plus initial and final bearings for up to 100 coordinate pairs, and optionally checks a claimed distance within a tolerance. Vincenty is millimetre-accurate except for nearly antipodal pairs, where it does not converge: those pairs return vincentyMeters null, status unknown and the haversine

Input parameters:

- `claimBasis` (string): Which distance claimedMeters is compared against (default vincenty).
- `pairs` (array, required): Coordinate pairs.
- `toleranceMeters` (number): Allowed difference for claimedMeters (default 1).

### `metar-parse` (~142 tokens)

METAR / SPECI decoder with flight category — Decodes up to 20 METAR or SPECI aviation weather reports (US and ICAO forms: wind with gusts and variable direction, visibility in statute miles or metres, CAVOK, RVR, present weather, cloud layers, temperature/dew point, altimeter, trend, RMK remarks) into structured fields and computes the FAA flight category (LIFR/IFR/MVFR/VFR). Every token it cannot decode is returned with its character offset

Input parameters:

- `claims` (array): Optional claims to verify against the decoded report.
- `reports` (array, required): Reports to decode.

### `chess-move` (~139 tokens)

Chess move legality, SAN/UCI conversion and next FEN — Checks whether a move (or a sequence of moves) is legal from a FEN position under the FIDE Laws of Chess, for agents that play, annotate or verify chess games. Accepts UCI or SAN, returns the normalized move, the new FEN, check / checkmate / stalemate / insufficient-material flags and, if asked, every legal move; an illegal move names the reason (castling_through_check, ep_exposes_king, moves_into

Input parameters:

- `items` (array, required): 1 to 50 positions, at most 400 moves in total.

### `dice-roll` (~251 tokens)

Verifiable dice roll from a seed, with a re-derivable transcript — Rolls dice notation (for example 4d6kh3+2) from a caller seed with a documented SHA-256 counter-mode stream and returns every die, the kept/dropped marks and a full draw transcript, for agents and referees that need a roll anyone can re-derive. Optionally checks a claimed total or claimed faces against the re-derived roll. Does NOT provide unpredictable randomness: the seed is public input, so any

Input parameters:

- `expectRolls` (array): Optional claimed faces in notation order, before keep/drop marks.
- `expectTotal` (integer): Optional claimed total to verify.
- `includeTranscript` (boolean): Default true. False drops blocks and draws (the transcript digest stays).
- `notation` (string, required): Dice notation: terms of NdM (N 1-100, M 2-1000) or integers joined by + and -; optional kh/kl/dh/dl with a count on a group. At most 20 groups and 1000 dice.
- `seed` (string, required): Caller seed string. Public: the outcome is a pure function of notation and seed.

### `score-state` (~179 tokens)

Score state for tennis, golf handicap differentials and cricket overs — Replays a tennis point sequence (ITF Rules of Tennis: games, deuce, tie-breaks, match tie-break, who serves), computes a golf Score Differential and Handicap Index (World Handicap System), or tallies a cricket innings ball by ball (overs.balls, wides and no-balls, maidens, wickets), for agents that must verify a reported score. Optionally checks a claimed score against the replay and names the fir

Input parameters:

- `cricket` (object): For sport=cricket: one innings, ball by ball.
- `golf` (object): For sport=golf: a round, a list of differentials, or both.
- `sport` (string, required): Selects which block below is read.
- `tennis` (object): For sport=tennis.

### `chord-check` (~272 tokens)

Chord check: identify, spell, key membership, transpose — Names a chord from its notes, spells a chord symbol into notes, tests whether a chord is diatonic to a key, or transposes a chord symbol, using pitch-class arithmetic over a fixed table of 21 chord qualities, for agents handling lead sheets and music metadata. Rule-based and labelled: when several readings are equally valid (C E G A is C6 or Am7/C) or no quality in the table matches, it returns un

Input parameters:

- `chord` (string): Chord symbol, root A-G with optional #/b, quality suffix, optional /bass: Cmaj7, F#m7b5, Bb/D.
- `expectChord` (string): Optional claimed chord symbol to verify (identify, transpose).
- `expectNotes` (array): Optional claimed notes in order, to verify (spell).
- `key` (object): For key-membership.
- `notes` (array): For identify: 2 to 8 notes.
- `operation` (string, required)
- `prefer` (string): Accidentals for a natural root when transposing. Default sharps; a root written with # or b keeps its kind.
- `semitones` (integer): For transpose: semitones up (negative down).

### `electrical-calc` (~617 tokens)

Electrical arithmetic and resistor colour codes — Computes Ohm's law and power from any two of V, I, R, P; series and parallel resistance with optional tolerance bounds; a voltage divider (with optional load); an LED series resistor rounded up to a preferred E-series value; conductor voltage drop from a caller-supplied resistivity; decodes or encodes 3 to 6 band IEC 60062 resistor colour codes; and tests whether a value is an official E3 to E192

Input parameters:

- `areaMm2` (number): line-drop: conductor cross-section in mm^2.
- `bandCount` (integer): colour-encode: 3, 4 (default), 5 or 6 bands. 5 and 6 bands carry three digits.
- `bands` (array): colour-decode: 3 to 6 colours read from the head end.
- `claim` (object): Optional map from an output value name (e.g. resistance, vout, minResistance) to the number you expect.
- `claimTolerancePct` (number): Relative tolerance for claim values, percent (default 0: exact).
- `current` (number): ohm, led-resistor, line-drop: amperes.
- `forwardVoltage` (number): led-resistor: LED forward volts.
- `lengthM` (number): line-drop: one-way length in metres.
- `maxDropPercent` (number): line-drop: fail when the drop exceeds this percent of supplyVoltage.
- `op` (string, required): ohm | series | parallel | divider | led-resistor | line-drop | colour-decode | colour-encode | e-series.
- `power` (number): ohm: watts.
- `r1` (number): divider: top resistor, ohms.
- `r2` (number): divider: bottom resistor, ohms.
- `rLoad` (number): divider: optional load across r2, ohms.
- `resistance` (number): ohm: ohms. colour-encode and e-series: the value in ohms.
- `resistances` (array): series/parallel: ohms, at most 100.
- `resistivityOhmM` (number): line-drop: conductor resistivity in ohm-metres, supplied by the caller (not looked up).
- `roundTrip` (boolean): line-drop: count out and return conductors (default true).
- `series` (string): led-resistor (default E24) and e-series: preferred-value series.
- `supplyVoltage` (number): led-resistor: supply volts. line-drop: optional, enables dropPercent.
- `tcrPpm` (number): colour-encode with 6 bands: temperature coefficient in ppm/K.
- `tolerancePct` (number): series/parallel: shared tolerance percent for min/max bounds. colour-encode: tolerance percent to encode.
- `vin` (number): divider: input volts.
- `voltage` (number): ohm: volts.

### `tolerance-stack` (~231 tokens)

One-dimensional tolerance stack-up (worst-case and RSS) — Computes the minimum and maximum of a linear dimensional stack (the gap) from signed contributions with symmetric, unequal-bilateral, unilateral or min/max limits, both by exact worst-case arithmetic and by root-sum-square, names the dominant contributor and tests the gap against a required minimum and/or maximum. For mechanical designers and agents checking clearances. It does not do 2D or 3D sta

Input parameters:

- `dimensions` (array, required): At most 100. Give nominal with tol, or nominal with plus and/or minus (unilateral: one of them), or min and max.
- `method` (string): Which result decides status against the requirement (default worst-case). Both are always reported.
- `reportSigma` (number): RSS: report the gap at this many sigma (default equals sigmaLevel).
- `requirement` (object): Allowed gap range.
- `sigmaLevel` (number): RSS: each tolerance is this many sigma (default 3).
- `unit` (string): Label for the single unit all numbers share (not converted).

### `carton-fit` (~144 tokens)

Pack items into the smallest fitting carton (bounded heuristic) — Checks whether up to 50 box-shaped items (axis-aligned, 90-degree rotations, optional this-side-up lock, optional weights) fit into any of up to 20 candidate cartons, and recommends the smallest-volume carton for which a packing was found, with coordinates for every item. For shipping and fulfilment agents sizing a parcel. The packing is a greedy extreme-point HEURISTIC with a fixed step cap, not

Input parameters:

- `boxes` (array, required): At most 20. Use inner dimensions.
- `items` (array, required): At most 50 item lines and 50 units in total (sum of qty).

### `lot-pick` (~333 tokens)

Choose which inventory lots to pick (FIFO, FEFO, LIFO, fewest lots) — Allocates a demand quantity across up to 200 inventory lots under a stated policy (FIFO by received date, FEFO by expiry, LIFO, or fewest lots), excluding held, expired, short-shelf-life and wrong-location lots, in whole case multiples if asked. For warehouse and order agents. Returns the pick plan, the shortfall and a reason for every excluded lot. A caller asOf date is required (the check never

Input parameters:

- `allowOverpick` (boolean): With pickMultiple, allow the last pick to round the total up to a whole case (default false: leave the remainder as shortfall).
- `allowedLocations` (array): If set, lots elsewhere (or without a location) are excluded.
- `asOf` (string, required): Reference date, YYYY-MM-DD. An expiry date is the last usable day: a lot expiring on asOf has 0 days left.
- `demand` (integer, required): Units wanted (whole units).
- `lots` (array, required): At most 200.
- `minShelfLifeDays` (integer): Exclude lots with fewer than this many days left at asOf (needs expiry on every non-held lot).
- `pickMultiple` (integer): Each lot contributes whole multiples of this case size (default 1).
- `policy` (string, required): FIFO: oldest received first. FEFO: earliest expiry first. LIFO: newest received first. MIN_LOTS: fewest lots (largest usable first; ties by earlier expiry, then id).

### `clause-tag` (~154 tokens)

Rule-based clause tagging (obligation, prohibition, permission, condition, topic) — Tags each contract-style clause you supply with the modal force it expresses (obligation, prohibition, permission, recommendation) and topic cues (definition, condition, termination, payment, confidentiality, liability, governing law, notice, assignment), with the matched cue and its offset. For an agent that must triage many clauses before a human or model reads them. Fixed cue phrases only (plus

Input parameters:

- `clauses` (array, required): Up to 100000 characters in total.
- `expect` (array): Tags a clause must carry; a missing one fails.
- `extraCues` (array): Your own cue phrases, matched as literal word sequences.

### `syllable-count` (~157 tokens)

Syllable counts per line, caller dictionary first, labelled English heuristic second — Counts syllables per word and per line for English text, using your dictionary entries first and otherwise a rule-based estimator (vowel groups, silent e, -ed/-es, consonant+le). Optionally checks each line against a target pattern such as 5-7-5. Where the rules cannot decide (vowel pairs like ia/io/eo, acronyms, numerals, non-Latin scripts) the word is a range or abstains, and a line whose count

Input parameters:

- `dictionary` (array): Caller counts; they override the rules.
- `lines` (array, required)
- `pattern` (array): Same length as lines.

### `requirement-coverage` (~167 tokens)

Checklist coverage: caller requirements against caller evidence — Evaluates a checklist of requirements the caller defines (each made of needs on evidence keys: present, equals, one of, min/max, maximum age) against evidence the caller supplies, and returns met / unmet / unknown per requirement with the exact need and value that decided it. For an agent that must prove a task's acceptance criteria were covered before it reports done. Does not judge whether the p

Input parameters:

- `asOf` (string): Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.
- `evidence` (array, required): Observed facts. Several items may share a key (conflicts surface as unknown).
- `requirements` (array, required): The checklist.

### `site-access-check` (~195 tokens)

Site access: caller access rules against observed site facts — Checks whether an intended action on a website (read, crawl, submit, log in, ...) satisfies the access rules the caller supplies (robots rule read, terms clause, login present, rate-limit budget, captcha seen) against facts the caller observed, and says which rule blocked it or which fact is missing. For an agent deciding whether to proceed or ask. It is a reading of the caller's rules, not legal

Input parameters:

- `action` (string, required): The intended action, matched against each rule's appliesTo.
- `asOf` (string): Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.
- `evidence` (array, required): Observed site facts.
- `rules` (array, required): Access rules: needs that must hold, or with forbid:true, conditions that must not apply.

### `pod-sufficiency` (~195 tokens)

Proof-of-delivery sufficiency against a required evidence list — Checks whether the proof-of-delivery evidence supplied (signature, photo, timestamp, GPS fix, recipient name, scan ...) satisfies the carrier or contract requirement list the caller gives: every required item, plus optional 'at least k of these' groups, with value bounds (for example GPS accuracy at most 30 m) and maximum age. For an agent assembling a delivery dispute or a payment release. Return

Input parameters:

- `anyOf` (array): Alternative groups: at least atLeast (default 1) of the keys must be present.
- `asOf` (string): Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.
- `evidence` (array, required): Proof elements the caller holds.
- `required` (array, required): Evidence every proof must contain (key plus optional bounds).

### `manual-applicability` (~153 tokens)

Does this manual or procedure apply to this unit? — Checks whether a manual, service bulletin or procedure applies to a specific unit by comparing the scope the document declares (models, firmware or revision range, serial range, exclusions) with the unit's facts the caller supplies. Versions written as dotted digits (2.10.1) compare numerically per segment. For an agent about to follow a repair or configuration procedure. Applicable only when ever

Input parameters:

- `applicability` (array, required): Scope the document declares: every entry must match.
- `excludes` (array): Scope the document excludes: each entry that matches makes it inapplicable.
- `unit` (array, required): The unit's facts: key is the field name.

### `document-supersession` (~191 tokens)

Is this document still current, or superseded by a newer one? — Given the target document id, the supplied set of documents (id, effective date, which ids each one supersedes, withdrawn flag) and a reference date, reports whether the target is superseded or withdrawn as of that date, following supersession chains, and names the superseding document and its date. For an agent about to rely on a standard, price list, policy or datasheet revision. It can only see

Input parameters:

- `asOf` (string, required): Reference date: a superseding document counts only if effective on or before it.
- `documents` (array, required): The documents the caller knows of, including the target.
- `listComplete` (boolean): The caller asserts documents holds every document that could supersede the target. Required for a pass.
- `target` (string, required): Id of the document being relied on.

### `transcribe-url` (~208 tokens)

Transcribe an audio or video file URL (Whisper, timestamps, SRT, VTT) — Transcribes a public audio or video FILE URL (podcast enclosure, meeting recording, voice memo; mp3, wav, mp4/m4a, ogg, webm, flac; up to 25 MB and 30 minutes) with Whisper large-v3-turbo on Cloudflare Workers AI. Returns timestamped segments plus SRT and VTT subtitles and the plain text, bound to the media's SHA-256. Does NOT accept YouTube, Spotify or any streaming page (the URL must be the medi

Input parameters:

- `formats` (array): Outputs to include; default all.
- `language` (string): ISO 639-1 language code of the speech (for example en); detected when omitted.
- `max_minutes` (integer): Reject audio longer than this, default 30.
- `url` (string, required): https URL of the audio or video file itself.

### `company-identity` (~285 tokens)

Company identity: name, domain, LEI, VAT, CIK or ticker to one verified legal entity — Resolves a company name, web domain, LEI, EU VAT number, SEC CIK or stock ticker to one legal entity using official free registries in a single call: GLEIF (legal name, other names, addresses, jurisdiction, registry id, direct and ultimate parent), the SEC ticker table (CIK, ticker), the EU VIES VAT service, and Companies House officers when the operator has configured a key. Deterministic matchin

Input parameters:

- `cik` (integer): SEC Central Index Key.
- `country` (string): ISO 3166-1 alpha-2 hint; raises the score of candidates registered in that country.
- `domain` (string): Company web domain; only used to guess a name and to prefer matching candidates. It is never fetched.
- `include_parents` (boolean): Look up GLEIF direct and ultimate parents.
- `lei` (string): 20-character LEI; check digits are validated (ISO 17442).
- `max_candidates` (integer): How many ranked candidates to return.
- `name` (string): Company name, with or without legal form.
- `ticker` (string): Stock ticker, matched case-insensitively against the SEC table.
- `vat` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 63
- 2026-11-19: 62
- 2026-11-18: 62
- 2026-11-17: 61
- 2026-11-16: 61
- 2026-11-15: 60

## Common questions

### What is the WritersLogic business agents MCP server?

WritersLogic business agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-business. Medical-bill audit, chargeback, contract terminator, lead enrichment, filing integrity. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/business).

### Is the WritersLogic business agents MCP server safe to use?

WritersLogic business agents scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the WritersLogic business agents MCP server expose?

WritersLogic business agents exposes 95 tools: lead-enrichment, competitor-battlecard, medical-bill-auditor, chargeback-fighter, contract-terminator, and 90 more. Their descriptions and schemas cost roughly 21,458 tokens of context every time the server is loaded.

### Does the WritersLogic business agents MCP server require authentication?

No. We connected to WritersLogic business agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WritersLogic business agents MCP server still maintained?

WritersLogic business agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the WritersLogic business agents MCP server?

VerifyMCP ran 12 checks on WritersLogic business agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about WritersLogic business agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agents.writerslogic.com/mcp/business
- Repository: https://github.com/writerslogic/ai-agents
- Website: https://writerslogic.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business.json
- HTML version of this page: https://verifymcp.io/servers/com-writerslogic-agents-writerslogic-business/mcp-business
