Skip to main content
Glama

PolySignals.net

How the readings are made

get_methodology
Read-only

The methodology document: what the score is, confidence, window matching, options readings, the backtest and the daily regime rule. Without a section: the list of sections and the introduction; with one: that section.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoA section title or part of one, for example 'confidence' or 'regime'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world behavior, so the description's job is lighter. It adds useful mode-dependent return behavior (index vs. specific section), which goes beyond the annotations, but omits edge cases like unmatched section names or output 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?

Two compact sentences with no filler, front-loaded with the resource identity before the mode behavior. The content enumeration is dense but each item earns its place by telling the agent what topics exist.

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?

With no output schema, the description carries return-shape burden and does so for both modes. It stops short of specifying format or error behavior for unknown sections, which would complete the picture for a low-complexity documentation tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the parameter acts as a mode switch between index view and single-section retrieval. It doesn't clarify partial-match semantics beyond the schema's example.

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?

States a specific resource (the methodology document) and enumerates its content areas: score, confidence, window matching, options readings, backtest, and regime rule. This clearly separates it from the data-returning siblings like get_coin_signal or get_regime, which return measurements rather than documentation.

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?

Explicitly describes the two calling modes: omit the section to get the section list plus introduction, pass one to get that section. This gives an agent clear context for how to invoke it, though it doesn't mention what happens if a section name isn't found.

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