Skip to main content
Glama
Kalshi Screener MCP

Kalshi Screener MCP

by kokogo100

Get the extension watchlist

get_watchlist
Read-only

Retrieves current prices for markets saved in your Chrome extension watchlist, helping you track and review Kalshi prediction-market selections.

Instructions

Current prices for the markets saved in the Chrome extension watchlist.

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": "get_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scoping context — this reads the user's Chrome-extension-saved watchlist rather than a server-side saved screen, and returns live prices — but says nothing about behavior with an empty watchlist or how many markets come back.

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?

A single efficient sentence with no filler, and the key qualifier (Chrome extension watchlist) is placed where it is read first. It is slightly nominal rather than verb-led, which makes it read like output documentation rather than an instruction to act.

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 zero-parameter read tool this is close to sufficient, and annotations carry the safety profile. With no output schema, though, the description should say more about the shape of the result (a list of markets with quote data?) so an agent knows what it will receive and whether an empty result is normal.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The schema itself is empty and fully covered.

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?

Names a specific resource (the Chrome extension watchlist) and states what is returned (current prices for the markets in it), which is more than a restatement of the name. It does not, however, distinguish itself from the closest sibling, list_saved_screens, so an agent must infer that watchlist and saved screens are different collections.

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

Usage Guidelines2/5

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

The description only documents what the tool returns; it never says when to call it, when not to, or which sibling to use instead (e.g. search_markets or list_saved_screens). Any usage guidance is left entirely to inference.

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