Skip to main content
Glama
Sign In
Limitless MCP

Limitless MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_conditions

Retrieve prepared on-chain market conditions and filter by resolution status to identify resolved or unresolved markets.

Instructions

Get conditions (markets that have been prepared on-chain) with resolution status. Useful for finding resolved/unresolved markets.

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

Input Schema

NameRequiredDescriptionDefault
resolvedNoFilter by resolution status
firstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Adds valuable domain context ('on-chain', 'resolution status') but omits behavioral details like pagination behavior, data freshness, or return structure that agents need when annotations are absent.

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 efficient sentences with no wasted words. Front-loaded with action and resource. Briefness appropriate for simple list operation, though content could be redistributed to cover the missing parameter documentation.

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?

Adequate for a simple 2-parameter listing tool. Explains the domain-specific term 'conditions' effectively, but gaps remain around the undocumented 'first' parameter andcomparison to numerous sibling market tools.

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

Parameters2/5

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

Schema coverage is only 50% (parameter 'first' undocumented). Description mentions 'resolution status' conceptually aligning with the 'resolved' parameter, but completely fails to document the 'first' parameter's purpose (likely pagination limit), providing no compensation for schema gaps.

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?

Clear verb ('Get') and resource ('conditions') with helpful parenthetical clarifying domain terminology ('markets that have been prepared on-chain'). However, lacks explicit differentiation from siblings like 'search_markets' or 'get_market_lifecycle'.

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?

States utility ('Useful for finding resolved/unresolved markets') implying when to use, but provides no explicit comparison to alternative tools or exclusion criteria (e.g., when to prefer search_markets instead).

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