Skip to main content
Glama
Sign In
SimpleFunctions

SimpleFunctions

by spfunctions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_markets

Retrieve live prediction market contracts with current YES/NO prices, 24h volume, and metadata. Filter by topic (energy, rates, fx, equities, crypto, volatility) for deep dives. Read-only, no authentication required.

Instructions

List live prediction market contracts with current YES/NO prices, 24h volume, and metadata. Read-only, no auth. Use for deep dives on a specific topic; use search_markets if you have a keyword instead of a topic, or get_context for a high-level overview.

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_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic filter. Allowed values: energy, rates, fx, equities, crypto, volatility. Omit for all topics.
limitNoMax contracts to return. Default 50. Hard cap 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / limit / description
      Added value: +"Max contracts to return. Default 50. Hard cap 500."
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / topic / description
      Previous value: -"Filter: energy, rates, fx, equities, crypto, volatility"New value: +"Topic filter. Allowed values: energy, rates, fx, equities, crypto, volatility. Omit for all topics."
  2. Addedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It explicitly states 'Read-only, no auth', which is sufficient for a simple listing tool. However, it omits details like rate limits or response format, which would add safety margin.

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 waste: purpose, read-only claim, and usage guidance in a logical order. Every sentence adds value, making it highly efficient.

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?

The description covers what the tool returns (prices, volume, metadata) and when to use alternatives. With only 2 parameters and no output schema, the description provides adequate context. It could mention pagination but is still sufficient.

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 baseline is 3. The tool description does not add any parameter detail beyond what is already in the schema. It does not explain syntax, constraints, or examples, so it neither helps nor harms.

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 starts with a clear verb ('List') and specifies the resource ('live prediction market contracts') and included data ('YES/NO prices, 24h volume, metadata'). It explicitly differentiates from siblings by naming search_markets and get_context, making purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Use for deep dives on a specific topic', and names two alternatives (search_markets with keyword, get_context for overview). This clearly sets usage boundaries.

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

Deploy Server

Other Tools