Skip to main content
Glama

Commodity Edge (Gold / Silver / Oil / Bitcoin)

commodity_edge
Read-only

Use for "gold edge today" and "oil or bitcoin trade signal". The Kalshi daily gold, silver or WTI strike, or hourly bitcoin strike, with the largest PMP model edge, as a ticket: side, entry price, resolve criterion, model probability, edge, tier and quarter-Kelly size. Pass tickers[] to check a watchlist. Pro — sign in with PredictionMarketsPicks, or a Pro API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "commodity_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersNoOptional Kalshi ticker watchlist (up to 25), market or event tickers. Unmodeled tickers return not_covered.
commodityNoWhich commodity edge to read (needed for a real answer). One of: silver · bitcoin · gold · oil.

Output Schema

NameRequiredDescriptionDefault
as_ofNoWhen the model ran.
ticketNoPro: side, entry price, resolve criterion, model probability, edge, tier, quarter-Kelly.
sourcesNo
has_edgeNoWhether the current run cleared the model.
commodityNogold, silver, oil or bitcoin.
tell_userNoShow this sentence to the user first.
timestampNo
resolutionNoticket / no_edge / no_run / off_hours / off_hours_15m / engine_stale / unavailable / wall / needs_input.
fifteen_minNoThe live 15-minute row when the daily/hourly read is not available.
needs_inputNo
example_callNo
data_freshnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": {},
      +  "properties": {
      +    "as_of": {
      +      "description": "When the model ran."
      +    },
      +    "commodity": {
      +      "description": "gold, silver, oil or bitcoin."
      +    },
      +    "data_freshness": {},
      +    "example_call": {},
      +    "fifteen_min": {
      +      "description": "The live 15-minute row when the daily/hourly read is not available."
      +    },
      +    "has_edge": {
      +      "description": "Whether the current run cleared the model."
      +    },
      +    "needs_input": {},
      +    "resolution": {
      +      "description": "ticket / no_edge / no_run / off_hours / off_hours_15m / engine_stale / unavailable / wall / needs_input."
      +    },
      +    "sources": {},
      +    "tell_user": {
      +      "description": "Show this sentence to the user first.",
      +      "type": "string"
      +    },
      +    "ticket": {
      +      "description": "Pro: side, entry price, resolve criterion, model probability, edge, tier, quarter-Kelly."
      +    },
      +    "timestamp": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / tickers / description
      Previous value: -"Optional Kalshi ticker watchlist (up to 25) — e.g. paste the tickers from your Kalshi Pro screener or Canvas to get PMP's edge on exactly those markets. Full market or 3-segment event tickers both work. Tickers PMP doesn't model are returned as not_covered (never a fabricated edge)."New value: +"Optional Kalshi ticker watchlist (up to 25), market or event tickers. Unmodeled tickers return not_covered."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive behavior. The description adds the Pro authentication requirement and enumerates the ticket fields returned, which is useful context beyond the annotations. It does not cover rate limits or not_covered handling in prose, but the schema does.

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?

The description is front-loaded with trigger examples, then gives output shape, watchlist behavior, and auth. The field list is dense but earns its place because it explains the ticket payload.

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?

For a two-parameter, read-only lookup with an output schema, the description covers purpose, output composition, watchlist use, and auth. Details like missing-commodity behavior and not_covered responses are handled in schema, so the definition is complete enough.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters. The description still adds meaning by mapping oil to the WTI strike and bitcoin to the hourly strike, and by framing tickers[] as a watchlist check.

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 states a specific verb and resource: it returns the Kalshi commodity strike with the largest PMP model edge as a structured ticket. The named commodities and the daily gold/silver/WTI and hourly bitcoin framing make it distinguishable from generic EV or probability siblings.

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 concrete trigger phrases such as 'gold edge today' and 'oil or bitcoin trade signal', plus an alternate watchlist mode via tickers[]. It does not state when to avoid this tool or explicitly route to siblings like calculate_ev or kelly_size, so it stops short of full when/when-not guidance.

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.