Perch Data

perchpermits/tennis-matches-odds-form

perchpermits--tennis-matches-odds-form

Destructive

This tool calls the Actor "perchpermits/tennis-matches-odds-form" and retrieves its output results. Actor description: ATP and WTA matches for any day, live or finished, with 15+ bookmakers' opening and current odds, rankings, last-10 form, surface record, and head-to-head in one JSON row per match. Filter by tour, tournament, player. Built for betting models and AI agents. $0.02 per enriched match.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	ISO date (YYYY-MM-DD). Defaults to today (UTC). Dates are the site's Central European calendar day.
`days`	No	How many consecutive days to list, starting at `date`. 1 to 14. Example values: 1
`mode`	No	`schedule` lists the day's upcoming, live, and completed matches. `results` lists only finished matches for the day. `live` lists only matches in progress right now, with the current set scores (a snapshot; run again for an update). `live` ignores `date` and `days`. Example values: "schedule"	schedule
`tour`	No	ATP (men), WTA (women), or both. Includes Challenger, ITF, and UTR events listed under each tour. Example values: "all"	all
`enrich`	No	Fetch every match's detail page: round, surface, rankings, this year's W/L by surface, head-to-head history, 15+ bookmakers' current and opening odds, both players' latest matches and form. Charged as `enriched-match` instead of `match`. Example values: true
`player`	No	Case-insensitive substring of either player's listed name, e.g. `Alcaraz`.
`status`	No	Keep only matches in this state. Leave empty for all.
`doubles`	No	Return doubles matches instead of singles.
`preview`	No	Add a `preview` field to each enriched row: 90 to 140 words by Claude on what the row's own numbers say (market, movement, form, surface, head-to-head). No pick, no invented facts. Charged as `match-preview` on top of `enriched-match`, only for rows that got one. Needs `enrich`.
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`maxMatches`	No	Stop after this many matches. Each enriched match is one extra request (about one second). Example values: 50
`tournament`	No	Case-insensitive substring of the tournament name, e.g. `US Open`, `Challenger`, `Wimbledon`.
`oddsHistory`	No	Add every recorded odds change per bookmaker (timestamped, site time). Larger rows.
`latestMatches`	No	How many recent matches to include for each player when enriching (1 to 30). Example values: 10
`archiveDatasetName`	No	Optional. Name of a dataset in your account to append every returned row to, so scheduled runs build a history that outlives run-data retention. Not charged again.
`requestDelaySeconds`	No	Politeness delay toward the source site. Lower is faster but risks throttling. Example values: 0.4

Output Schema

TableJSON Schema

Name	Required	Description
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 19, 2026
- changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / enrichment / properties / h2h / properties / matches / items / properties / score / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
- changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / enrichment / properties / h2h / properties / matches / items / properties / surface / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
- removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / result_note
```
Removed value: -{
-  "type": "string"
-}
```
First observedSep 19, 2026

TDQS

A3.5/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description frames the operation as retrieval: 'calls the Actor ... and retrieves its output results,' while annotations mark readOnlyHint=false and destructiveHint=true. It also fails to disclose the paid run side effects, wait/poll behavior, or dataset-appending behavior implied by waitSecs and archiveDatasetName. This is an annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the wrapper behavior, and packs the actor's value proposition into the second sentence without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter actor-invoking tool with an output schema, the overview plus cost is useful, but it omits the run lifecycle and side-effect context that would reconcile the description with its annotation flags and parameters like waitSecs and archiveDatasetName.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the input schema. The description adds only high-level filter mentions and pricing, which does not materially exceed the schema's baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the exact Actor and, in the Actor description, names the resource and output: 'ATP and WTA matches for any day, live or finished... one JSON row per match.' This is a specific verb-resource pairing and clearly distinguishes it from sibling tools like the weather-market or store-trends tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context: 'Filter by tour, tournament, player' and states it is 'Built for betting models and AI agents.' It does not explicitly contrast against alternatives or say when not to use it, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Perch Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.