Skip to main content
Glama

pronto-stream

by io.github.nmxmxh

get_latest_signals

Read-onlyIdempotent

Fetch the most recent live signals from the wire in token-efficient CWF format, optionally filtered to one collection.

The all-collections view is diversified: no provider may exceed its share of the page, no collection may take more than half of it, and what overflows is named on a note line rather than dropped silently — so a burst of tickers cannot crowd out earthquakes. Pass collection to read one collection at full depth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of signals to return (default 20, max 100)
cursorNoPage token from META cursor: of the previous response. Omit for the first page.
relateNoAlso return the link graph over the rows in this response, as REL and CLUSTER lines, so repeats of one story collapse into one line without a second call. Off by default.
collectionNoSignal collection to filter by, e.g. climate, sentiment, security, health, cosmic, energy, macro, market, crypto, knowledge, prediction, logistics. Omit for all collections.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Page token from META cursor: of the previous response. Omit for the first page.",
+  "type": "string"
+}
    • changedInput schema / properties / relate / description
      Previous value: -"Also return the link graph over the rows in this response, as REL lines, so repeats of one story can be collapsed without a second call. Off by default."New value: +"Also return the link graph over the rows in this response, as REL and CLUSTER lines, so repeats of one story collapse into one line without a second call. Off by default."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare readOnly, openWorld, and idempotent hints, so no mutation warning is needed. The description then adds valuable non-obvious behavior: the all-collections view enforces caps, anything overflowing is named on a note line, and collection filtering changes the depth/diversification of results. This gives the agent important expectations about response shape beyond the schema.

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?

The core action is front-loaded in the first sentence, and every subsequent clause earns its place by explaining decision-relevant behavior about diversification, overflow handling, and collection-specific depth. The form is compact despite the colorful phrasing, and no redundant or filler material is included.

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?

For a read-only list tool with no output schema, the description covers the tool's scope, filtering modes, output lineage ('CWF format', note lines), and key behavioral caveats. It does not spell out the full CWF line syntax or explicitly explain parsing after receiving the response, which would deepen completeness, but it is sufficient for correct selection and invocation.

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 because every parameter already has a description. The description adds genuine extra meaning for collection=...: 'full depth' with a single collection versus a diversified all-collections view. This nuance is not present in the schema alone and meaningfully changes invocation choices.

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?

The description clearly states a specific verb and resource: 'Fetch the most recent live signals... optionally filtered to one collection.' It conveys the live, time-sensitive nature of the tool, which distinguishes it from sibling tools like get_signal, get_fused_signal, or search_signals. Even without naming siblings explicitly, the resource and freshness framing make its role unambiguous.

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?

The description gives clear contextual guidance: the all-collections view is deliberately diversified, while passing collection switches to full-depth/full-volume reading. It tells the agent when each mode is appropriate. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls just short of fully explicit routing.

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

All pronto-stream toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct operation: the two facet-listing tools are explicitly differentiated as quick manifest vs exhaustive listing, and search_signals vs scope_signals is cleanly split between lexical search and facet filtering. The billing/payment tools also form a clear lifecycle with no overlapping responsibilities.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: get_* and list_* for reads, and action verbs like register_agent, open_payment, settle_payment, scope_signals, search_signals for operations. No mixed casing or inconsistent verb styles.

Tool Count5/5

15 tools is at the upper edge of the well-scoped range but each tool earns its place: five cover data retrieval, four cover discovery/metadata, and five cover identity/billing. No redundant or filler tools.

Completeness5/5

The surface covers the full workflow for the stated domain: discover vocabulary, search/scope the live wire, retrieve individual signals and related signals, compute fused products, register an identity, and purchase/activate a plan. The only apparent omissions, such as cancellation, are outside the described prepaid self-service flow.

Resources