Skip to main content
Glama

Look up one market's match

lookup_match
Read-onlyIdempotent

Find the same bet on another venue for one market you know: its twin, how confident the match is, the rule differences, and both venues' live prices. Once the market has settled, says how both venues settled it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "<venue>",
      "market_id": "<market_id>"
    },
    "name": "lookup_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNoFor a Kalshi market: which venue to find its twin on. Polymarket US when left out.
venueYesThe venue the market id is from.
market_idYesThe market's id on that venue: Kalshi's market ticker, Polymarket's conditionId or slug, Polymarket US's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real value beyond that by disclosing what the call returns (twin match, confidence, rule differences, both venues' live prices) and that it still works after settlement, which the annotations cannot convey. It stops short of describing pagination or failure behavior when no twin exists.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action, and every clause enumerates a distinct piece of returned information. The post-settlement clause is slightly awkwardly phrased ('says how both venues settled it') but still earns its place by covering a second use case.

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

Completeness4/5

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

There is no output schema, so the description must sketch the return value, and it does so concretely (twin, confidence, rule differences, live prices, settlement). For a 3-parameter read-only lookup with full schema coverage, that is close to complete; only no-match behavior is left unstated.

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% and both enums are documented inline, so the schema carries parameter meaning. The description only reinforces that the lookup is scoped to one known market and says nothing extra about the 'with' override or accepted id formats, 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 gives a specific verb ('Find the same bet on another venue') and names the resource (one market's twin), plus it enumerates what comes back: confidence, rule differences, live prices, and settlement. The phrase 'for one market you know' implicitly separates it from a bulk finder like find_matches, though it never names the sibling.

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

Usage Guidelines3/5

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

'For one market you know' implies the preconditions (you already hold a venue and market id) and suggests when a single lookup is appropriate rather than a broad search. There is no explicit when-not guidance and no alternative tool named, so the agent must infer the routing to find_matches from the sibling's name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources