Skip to main content
Glama
Sign In
SimpleFunctions

SimpleFunctions

by spfunctions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_world_delta

Retrieve only prediction markets whose probability changed since a specified timestamp. Use for efficient polling loops instead of fetching full world state. Specify lookback window or ISO timestamp.

Instructions

Incremental diff of the world model since a given timestamp — only the markets whose probability moved. ~30-50 tokens vs ~800 for the full state from get_world_state. Read-only, no auth. Use this for cheap polling loops; use get_world_state for an absolute snapshot.

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": {
      "since": "<since>"
    },
    "name": "get_world_delta"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesLookback window. Either a relative duration (30m, 1h, 6h, 24h) or an ISO-8601 timestamp. Required.
formatNoOutput format. Default: markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / format / description
      Added value: +"Output format. Default: markdown."
    • changedInput schema / properties / since / description
      Previous value: -"Relative (30m, 1h, 6h, 24h) or ISO timestamp"New value: +"Lookback window. Either a relative duration (30m, 1h, 6h, 24h) or an ISO-8601 timestamp. Required."
  2. Addedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses key behaviors: read-only, no authentication required, and token size estimate (~30-50 tokens vs ~800). With no annotations, the description fully handles transparency for this simple read tool.

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 tight sentences with no filler. The key concept is front-loaded, and every sentence adds value without redundancy.

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?

For a simple tool with 2 parameters and no output schema, the description covers purpose, usage, behavioral specifics, and sibling comparison. No gaps for an agent to misinterpret.

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 good parameter descriptions. The tool description adds no extra parameter-specific meaning beyond what the schema already provides, so baseline of 3 is appropriate.

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 identifies the tool as an incremental diff of the world model, specifying it returns only markets with probability movement. It explicitly contrasts with sibling get_world_state, distinguishing cheap polling from absolute snapshots.

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?

Provides explicit guidance: 'Use this for cheap polling loops; use get_world_state for an absolute snapshot.' Clearly states when to use this tool and when to use the 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