MarketPulse MCP

check_signal_outcomes

Force-check pending signal outcomes past their 7-day or 30-day window. Returns number of signals updated.

Instructions

Manually trigger outcome checking for all pending signals.

Normally runs automatically, but you can call this to force-check any signals whose 7-day or 30-day window has elapsed.

Returns how many signals were updated.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Aug 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it is a manual trigger, that it operates on pending signals with elapsed windows, and that it returns a count of updated signals. However, it does not explain potential side effects, irreversibility, or idempotency. The core behavior is clear, but depth is limited.

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?

The description is concise and front-loaded: the first sentence states the main action, the second provides context, the third gives the trigger condition, and the fourth states the return value. Every sentence earns its place with no redundancy.

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?

For a no-parameter tool with an output schema, the description covers the purpose, trigger condition, and return value. It is sufficiently complete for its simplicity. It could mention handling of signals that don't meet the window, but that is not essential.

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 has 0 parameters, so schema coverage is 100% (empty schema). The description does not need to explain parameters. Per the rubric, 0 params baseline is 4, and nothing reduces it.

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 tool's action with a specific verb and resource: 'Manually trigger outcome checking for all pending signals.' This unambiguously distinguishes it from sibling tools that handle quotes, analytics, or signal generation. The additional note about it normally running automatically clarifies its role as a manual override.

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

Usage Guidelines4/5

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

It explicitly says when to use this tool: 'you can call this to force-check any signals whose 7-day or 30-day window has elapsed.' This provides clear context for invocation, though it does not name specific alternatives or state when not to use it. The guidance is present but lacks exclusions.

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

Deploy Server