---
name: everyday-tools
description: Select and use Everyday MCP tools for deterministic everyday calculations and utilities. Use when a user needs an exact calculation, conversion, text utility, calendar helper, or timer supported by Everyday MCP.
compatibility: Requires an Everyday MCP remote connection at https://everyday.alfie.family/mcp
---

# Everyday Tools

Use the smallest Everyday MCP workflow that answers the user's request.

## Choose the tool

- Inspect the connected server's `tools/list` response before choosing among the 14 main tools.
- Use `everyday_calculate` for deterministic calculations.
- Keep the direct `recipe_scale`, `shopping_merge`, and `bill_split` actions inside `everyday_calculate` when one of those actions matches the request.
- For text, calendar, timer, subtitle, code, or other utilities, select the relevant advertised tool from `tools/list`.
- Do not reproduce or assume a complete tool directory in this skill.
- Do not make unrelated calls.

## Discover a calculator

The `everyday_calculate` tool exposes 67 calculators behind one stable interface.

1. Call `everyday_calculate` with request action `catalog` and a short query that describes the calculation.
2. Select the calculator whose description matches the user's goal.
3. Call action `describe` for that calculator ID.
4. Build action `calculate` parameters from the returned `inputSchema` and example.
5. If validation fails, use the error to identify the field at fault, fetch `describe` again, and rebuild the request from the current schema.

Do not invent calculator IDs or parameter names from memory. Skip discovery only when the current conversation already contains a fresh `describe` response for the same calculator and schema.

## Preserve exact inputs

- Send rational quantities and decimal money or rate fields as strings when the schema requires strings.
- Preserve the user's currency code, such as `USD` or `EUR`, and use only user-supplied prices, rates, fees, taxes, and exchange rates.
- Never guess live prices, tariffs, tax rates, or exchange rates.
- Treat US and Imperial volume and fuel-economy units as different systems.
- Include explicit units for every quantity that requires one.
- Do not silently convert an ambiguous unit.

## Present the result

For calculator results, report the relevant entries from all three result sections:

- `values`: the computed values.
- `units`: the unit or currency attached to each value.
- `assumptions`: model boundaries and user-supplied conditions.

State any additional assumption you introduced before relying on it. Ask for a missing input when different reasonable values would materially change the result.

## Examples

Read [references/examples.json](references/examples.json) when a concrete discovery-and-calculation request shape is useful. Its calls are complete MCP arguments and can be sent without placeholder substitution.