Skip to main content
Glama
Sign In
SimpleFunctions

SimpleFunctions

by spfunctions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_markets

Search prediction market contracts by keyword across question text and resolution criteria to find relevant markets quickly. Ideal for locating contracts with free-form terms like names or topics.

Instructions

Full-text search prediction market contracts by keyword across question text and resolution criteria. Read-only, no auth. Use when you have a free-form term ("OPEC", "Powell", "TSMC"); use get_markets if you only want to filter by predefined topic.

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": {
      "query": "<query>"
    },
    "name": "search_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keyword or phrase. Required, non-empty. Matches question text and resolution criteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2
  2. Removedv0.1.0
  3. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, but the description explicitly states 'Read-only, no auth', which discloses important behavioral traits. It could mention pagination or result limits, but for a simple search, this is sufficient.

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?

Two sentences, no redundancy, front-loaded with the core purpose. Every word earns its place.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description covers purpose, usage guidelines, and behavioral transparency completely. No gaps.

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 coverage is 100% with a descriptive parameter comment. The tool description essentially restates the schema's parameter info ('matches question text and resolution criteria'), adding no new meaning beyond what the schema provides.

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 clearly states the verb 'search' and the resource 'prediction market contracts', and specifies the scope 'by keyword across question text and resolution criteria'. It effectively distinguishes from sibling tool 'get_markets' which filters by predefined topic.

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?

Explicit usage guidance: 'Use when you have a free-form term' and explicitly contrasts with 'get_markets' for predefined topic filtering, providing clear when-to-use and alternative.

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