Skip to main content
Glama

CatalystDesk

scan_parameter_surface

Describe in-sample risk and return across caller-defined period pairs.

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>",
      "period_pairs": "<period_pairs>"
    },
    "name": "scan_parameter_surface"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
bar_typeNo
max_barsNo
period_pairsYes
bar_thresholdNo
include_overnightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions 'in-sample' as a trait, but omits critical details: whether the operation is read-only, what permissions are needed, computational cost, data requirements, or what the output 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.

Conciseness4/5

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

The description is a single sentence with no filler, front-loading the core purpose. However, its extreme brevity borders on under-specification for a tool of this complexity.

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 six parameters, a nested array of objects, no annotations, no output schema, and 0% schema description coverage. A one-sentence description cannot adequately convey what the tool returns, how risk and return are computed, or how to use the parameters correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the six parameters. It only indirectly references 'period_pairs' via 'caller-defined period pairs' and leaves ticker, bar_type, max_bars, bar_threshold, and include_overnight completely unexplained.

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 states a specific verb ('Describe') and resource ('in-sample risk and return') with the scope 'caller-defined period pairs.' It is clear what the tool does, but it does not differentiate itself from siblings like scan_curated_universe_regimes or compute_dynamic_regime, which likely also analyze risk/return or parameters.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only hint is 'in-sample,' which implies a backtesting context, but that is not explicit usage guidance.

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