# missed_call_roi

Calculate how much revenue a business loses to missed phone calls per month and per year, and which price tier of answering service makes sense at that loss level. Use when someone mentions missing calls, going to voicemail, losing leads after hours, or asks whether an answering service is worth it for their call volume. Inputs: calls per week, percent missed, average customer value, optional booking rate.

Agent View of the PolicyLayer registry record for `missed_call_roi`. HTML page: https://policylayer.com/tools/com-fitmycall-pricing/missed-call-roi

## Facts

- Tool: `missed_call_roi`
- Server: FitMyCall — Answering Service Prices (`https://mcp.fitmycall.com/mcp`) — https://policylayer.com/tools/com-fitmycall-pricing.md
- Homepage: https://github.com/https://mcp.fitmycall.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `callsPerWeek` | number | yes | Total inbound calls per week (1-2000) |
| `missedPercent` | number | yes | Percent of calls missed (0-100) |
| `bookRatePercent` | number | no | Percent of missed callers who would have booked; default 30 |
| `avgCustomerValue` | number | yes | Average value of one new customer in USD (1-100000) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "missed_call_roi",
    "arguments": {
      "callsPerWeek": 0,
      "missedPercent": 0,
      "avgCustomerValue": 0
    }
  }
}
```

## Why missed_call_roi is rated Low

Even though missed_call_roi only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call missed_call_roi to retrieve information from FitMyCall — Answering Service Prices without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FitMyCall — Answering Service Prices:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "missed_call_roi": {}
  }
}
```

## Other tools on FitMyCall — Answering Service Prices (3)

- `recommend_answering_service_for_industry` — Execute — https://policylayer.com/tools/com-fitmycall-pricing/recommend-answering-service-for-industry.md
- `get_answering_service_pricing` — Read — https://policylayer.com/tools/com-fitmycall-pricing/get-answering-service-pricing.md
- `compare_answering_services` — Write — https://policylayer.com/tools/com-fitmycall-pricing/compare-answering-services.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fitmycall-pricing · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fitmycall-pricing