Skip to main content
Glama

signals_evaluate

Pure-function alert evaluator. Caller passes snapshot + thresholds; returns {alert, matched, reason}. Same inputs -> same outputs. policy_version=evaluate-v1.

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

Input Schema

NameRequiredDescriptionDefault
assetsNoArray of asset objects (from signals_delta)
max_change_24hNoDefault -3 (percent)
min_volatilityNoDefault 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well: it declares purity ('pure-function'), determinism ('Same inputs -> same outputs'), the exact return shape, and a policy version for auditing. It omits only edge behavior such as how missing thresholds default or what failure looks like.

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?

Four short, front-loaded sentences with no filler: purpose first, then contract, then determinism, then policy version. Every sentence carries distinct information an agent would otherwise have to infer.

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 three-parameter, zero-required tool with no annotations and no output schema, the description supplies the return shape and the purity contract, which is what an agent most needs. Only the defaulting behavior for omitted thresholds (documented in schema, not description) and error cases are left unaddressed.

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 the schema already documents all three parameters; the description only adds a loose conceptual grouping ('snapshot + thresholds') without new syntax, ranges, or default semantics beyond what the schema states.

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?

The description names a specific verb and resource ('Pure-function alert evaluator') and states exactly what it consumes (snapshot + thresholds) and returns ({alert, matched, reason}). It is clearly distinguishable from data-fetching siblings, though it never names an alternative by name.

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?

Usage is only implied: the schema notes that assets come 'from signals_delta', which hints at the pipeline order, but the description itself gives no explicit when-to-use or when-not-to-use guidance relative to siblings like list_active_signals or signals_rank.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources