mcp-claudinho

Prediction-market signal

get_market_signal

Read-only

Retrieve read-only prediction-market percentages for a match, team fixture, or date, displayed before or during play with provider attribution.

Instructions

Read-only prediction-market signals for a match (by id), a team's current-or-next fixture, or a date (default: today). Returns market-implied percentages with attribution; complete:false means the provider read was incomplete, not that no signal exists. Shown only before and during a match — finished matches have no market read. Informational only — relay the numbers factually; do not add betting, trading, or 'value' advice, and do not invent links.

Input Schema

TableJSON Schema

Name	Required	Description
`tz`	No	IANA timezone for kickoff times, e.g. America/Mexico_City
`date`	No	Date as YYYY-MM-DD (default: today) for all that day's signals
`lang`	No	Locale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)
`team`	No	3-letter team code, e.g. MEX — resolves to the team's in-play match when one is live, else their next fixture
`flavor`	No	Commentary flair: off, subtle, full (default: full)
`matchId`	No	Match id (most specific)

Output Schema

TableJSON Schema

Name	Required	Description
`date`	No
`team`	No
`count`	No
`signal`	No
`matchId`	No
`signals`	No
`complete`	No	False when the market provider did not complete every relevant read
`degraded`	No
`truncated`	No
`informationalOnly`	Yes
`responseTruncated`	No
`responseTruncation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.10.0Sep 15, 2026

addedOutput schema / properties / complete

Added value: +{
+  "description": "False when the market provider did not complete every relevant read",
+  "type": "boolean"
+}

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / responseTruncated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / responseTruncation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedv0.9.0Jul 3, 2026

changedInput schema / properties / lang / description

Previous value: -"Locale for formatting: en, es, pt, fr (other locales fall back to en)"New value: +"Locale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "date": {
+      "type": "string"
+    },
+    "degraded": {
+      "type": "boolean"
+    },
+    "informationalOnly": {
+      "type": "boolean"
+    },
+    "matchId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "signal": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "signals": {
+      "items": {
+        "$ref": "#/properties/signal/anyOf/0"
+      },
+      "type": "array"
+    },
+    "team": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "informationalOnly"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / team / description

Previous value: -"3-letter team code for that team's next fixture, e.g. MEX"New value: +"3-letter team code, e.g. MEX — resolves to the team's in-play match when one is live, else their next fixture"

First observedv0.1.0Jun 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description explains the semantics of the complete field (incomplete read ≠ no signal), the availability window (only before/during match), and warns not to invent links or add betting advice. These are meaningful behavioral disclosures that annotations alone do not provide.

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?

Three sentences with no wasted words: the first front-loads the core purpose and query modes, the second clarifies a potentially confusing return field, and the third covers availability and usage constraints. Every sentence earns its place.

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

Completeness5/5

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

With an output schema present and readOnly/openWorld annotations, the description fills the key gaps: complete:false interpretation, the no-data-for-finished-matches constraint, and the informational-only usage. An agent has enough information to invoke the tool correctly.

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?

The input schema documents all six parameters with 100% coverage, including descriptions for team, matchId, and date. The description repeats the query-mode mapping but adds no parameter detail beyond what the schema already provides, so baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool returns read-only prediction-market signals and enumerates three query modes: match id, team's current-or-next fixture, and date. It identifies the resource type (market signals) distinctly from sibling data tools, though it does not explicitly name a sibling alternative.

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?

The description gives clear context for when to use the tool: before and during a match, and notes that finished matches have no market read. It also instructs to relay numbers factually and not add advice, which helps an agent decide when and how to invoke it. However, it does not explicitly contrast with siblings like get_match or get_next_fixture.

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

Deploy Server