Skip to main content
Glama

signals_rank

Deterministic ranking with published formula. risk_adjusted: abs(7d)/max(volatility,0.01). momentum: 0.51h+0.324h+0.2*7d. formula_version=rank-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_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses determinism, the exact ranking formulas, and formula_version=rank-v1, but it does not state whether the operation is read-only, what permissions are needed, or what the response contains.

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 front-loaded and compact: it states determinism, gives both formulas, and records the formula version without filler. The notation is terse but appropriate for a formula-focused tool.

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?

For a low-complexity ranking tool with one optional enum parameter and no output schema, the description covers the ranking logic and versioning. However, it leaves the ranked resource, default mode, and return shape unstated, so an agent still lacks some context needed to invoke it confidently.

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 single optional mode parameter has 0% schema description coverage, but the description compensates by defining both enum values with explicit formulas. It still omits the default mode when mode is not supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a deterministic ranking operation and publishes the exact formulas for both modes, but it never explicitly says what is being ranked (signals) or how this differs from siblings such as signals_evaluate or signals_delta. The operation is clear enough to identify, but the resource and sibling boundary remain implicit.

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

Usage Guidelines2/5

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

It explains the two mode formulas but gives no guidance on when to choose risk_adjusted versus momentum, nor when to use this tool instead of list_active_signals, signals_delta, or signals_evaluate. The agent must infer mode selection from the formulas alone.

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