# get_schedule

Footdigest: a competition's fixtures with teams, kickoff time, status, score, and stage. Give the competition slug; optionally filter by status (e.g. scheduled, live, finished) and cap with limit.

Agent View of the PolicyLayer registry record for `get_schedule`. HTML page: https://policylayer.com/tools/com-footdigest-footdigest/get-schedule

## Facts

- Tool: `get_schedule`
- Server: Footdigest (`https://footdigest.com/mcp`) — https://policylayer.com/tools/com-footdigest-footdigest.md
- Homepage: https://github.com/https://footdigest.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Max fixtures to return (default 20, max 100). |
| `status` | string | no | Optional status filter, e.g. finished. |
| `competition` | string | yes | Competition slug, e.g. world-cup-2026. |

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": "get_schedule",
    "arguments": {
      "competition": "<competition>"
    }
  }
}
```

## Why get_schedule is rated Low

get_schedule is a data retrieval function that queries and returns football match schedule information. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. The optional filtering parameters (status, limit) are read-only query constraints.

From the tool's own definition: "The tool description explicitly states it retrieves 'a competition's fixtures with teams, kickoff time, status, score, and stage' and allows optional filtering by status and limit."

## Use case

AI agents call get_schedule to retrieve information from Footdigest 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 Footdigest:

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

## Other tools on Footdigest (13)

- `simulate` — Execute — https://policylayer.com/tools/com-footdigest-footdigest/simulate.md
- `get_bracket` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-bracket.md
- `get_defining_moments` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-defining-moments.md
- `get_head_to_head` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-head-to-head.md
- `get_match` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-match.md
- `get_match_brief` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-match-brief.md
- `get_match_probabilities` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-match-probabilities.md
- `get_model_card` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-model-card.md
- `get_qualification_scenarios` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-qualification-scenarios.md
- `get_standings` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-standings.md
- `get_suspension_watch` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-suspension-watch.md
- `get_team_availability` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-team-availability.md
- `get_tournament_odds` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-tournament-odds.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-footdigest-footdigest · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-footdigest-footdigest