Skip to main content
Glama

CatalystDesk

compute_multiframe_resonance

Compare descriptive regime alignment across two to four frames.

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": {
      "ticker": "<ticker>",
      "frames": "<frames>"
    },
    "name": "compute_multiframe_resonance"
  }
}

Input Schema

NameRequiredDescriptionDefault
framesYes
tickerYes
include_overnightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Compute' and 'compare' weakly imply a read-only analytical operation, but the description does not state side effects, permissions, data-fetch behavior, latency, or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. Its terseness is a completeness problem rather than a conciseness problem.

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

Completeness2/5

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

The tool has a nested frame schema, no annotations, no output schema, and 0% parameter description coverage. One sentence stating only the basic comparison scope is far from sufficient for an agent to invoke this complex tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, including a nested frame configuration with bar_type, thresholds, and periods. The description only restates the frame count range from the schema and adds no meaning for ticker, frame fields, or include_overnight.

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 names a comparison operation and the resource area (descriptive regime alignment) with a 2-4 frame scope. However, the core terms 'alignment' and 'frames' are left undefined, and it does not explicitly distinguish this tool from sibling regime tools.

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 implies a multiframe comparison use case by limiting the operation to two to four frames, but gives no when-to-use guidance, prerequisites, or alternatives such as compute_dynamic_regime or get_regime_snapshot.

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