Skip to main content
Glama
Sign In
Frontier Signal MCP

Frontier Signal MCP

by collectivewinca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Demand mix

demand_mix
Read-onlyIdempotent

Retrieves hot demand categories and recorded mention counts from a public baseline for a specified date or the default committed cut, returning recorded data without inventing categories or counts.

Instructions

Return hot demand categories recorded on a public baseline.

mention_count values are heuristics copied from the JSON cut, not hit counts. This tool never invents additional categories or counts.

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

Input Schema

NameRequiredDescriptionDefault
observedNoBaseline date YYYY-MM-DD. Omit for the latest committed cut.

Output Schema

NameRequiredDescriptionDefault
hotYes
hot_noteNo
observedYes
disclaimerNoMention counts are heuristics recorded on the public baseline, not search-engine hit counts. Do not invent additional counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so safety is not the description's burden. It adds genuinely non-obvious behavior: mention_count is a heuristic copied from the source cut rather than a hit count, and the tool will not synthesize categories. That is exactly the kind of data-fidelity caveat an agent cannot infer from structured fields.

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 short sentences, no filler, with the return scope front-loaded and the caveat second. The line break mid-sentence and the slightly opaque phrase 'the JSON cut' cost it a point but nothing is redundant.

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?

With an output schema present and only one optional parameter, the description needs to carry little structural detail, and the fidelity caveat is a valuable addition. However, it leaves the central concept ('hot demand categories') undefined and says nothing about ordering, size, or coverage of the returned mix, which is the main thing an agent would need to interpret results.

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% and the single optional 'observed' parameter is documented there as YYYY-MM-DD with omit-for-latest semantics. The description's phrase 'public baseline' echoes the schema without adding format or defaulting detail, so the schema does the heavy lifting.

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 gives a concrete verb and resource ('Return hot demand categories') and scopes it to a 'public baseline', which separates it from siblings like list_observed_dates and deltas. What 'hot' means operationally is never defined, so the purpose is clear but not fully pinned down.

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 explicit when-to-use guidance: nothing says to prefer this over latest_brief or deltas, or when a baseline date should be supplied versus omitted. The only usage hint is implicit in the parameter description, which lives in the schema rather than the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools