Skip to main content
Glama

signals

Read-only

The live signal cards: compiled, provenance-carrying observations (lead_lag, network, signature) with severity and the entities they name. Cards appear only while their type is armed; an answer with no cards costs nothing. Observations, not advice. Agent keys only. Metered: see CHARGING in the server instructions; quote first with billing_quote.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOne signal family: lead_lag | network | signature. Default all three.
limitNoCards per answer, 1-50. Default 20.
countryNoTwo-letter ISO country code (e.g. DE); cards about entities in that country.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / country / default
      Removed value: -null
    • removedInput schema / properties / country / title
      Removed value: -"Country"
    • removedInput schema / properties / kind / default
      Removed value: -null
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"signalsArguments"
    • removedOutput schema / title
      Removed value: -"signalsDictOutput"
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare this a read-only, non-destructive, closed-world read, and the description still adds substantive behavior: the tool is metered, pricing is governed by CHARGING in server instructions, billing_quote should be called first, empty results are free, and results are gated on armed card types. It also sets expectations that output is observational, not advisory. These are exactly the cost, auth, and gating facts annotations cannot convey.

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?

Five short sentences, front-loaded with the identity and payload, followed by gating semantics, then cost and the billing_quote pointer. Nothing repeats the schema or annotations, and the telegraphic style ('Observations, not advice. Agent keys only.') is efficient rather than vague.

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 an output schema present, return format need not be described, and the description covers payload identity, cost behavior, auth, and gating. The remaining gap is the arming concept: it never says how a card type becomes armed or how to check arm state before paying for a possibly empty call. For a metered tool that gap matters, though the billing_quote pointer partially mitigates it.

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%, with kind, limit, and country all documented in the schema, so the baseline is 3. The description reinforces the family names and the 'entities they name' notion that underlies the country filter, but adds no format or interaction detail beyond that. It does not explain whether kind and country combine or how arming interacts with kind selection.

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 says exactly what the tool returns: live signal cards, described as compiled, provenance-carrying observations with severity and named entities, and it enumerates the three families (lead_lag, network, signature). That is a specific resource statement rather than a restatement of the name. It stops short of contrasting itself against nearby siblings such as oracle_assess or transparency_latest, so an agent must infer which is the right read surface.

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?

It states real preconditions: cards appear only while their type is armed, an empty answer costs nothing, agent keys are required, and the caller should quote first with billing_quote. That is clear context for when to call it and in what order. It gives no explicit exclusions or named alternatives among the many siblings, so the negative case is left implicit.

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