Skip to main content
Glama

Pronto

by stream.pronto.api

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. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of signals to return (default 100, max 500)"New value: +"Maximum number of signals to return (default 20, max 100)"
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of signals to return (default 20, max 100)"New value: +"Maximum number of signals to return (default 100, max 500)"
  4. Changed1 schema field changed
    • addedInput schema / properties / relate
      Added value: +{
+  "description": "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.",
+  "type": "boolean"
+}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses meaningful non-obvious behavior beyond the readOnly/openWorld/idempotent annotations: CWF format, provider and collection diversification caps, and overflow being named on a note line instead of silently dropped. This gives the caller a realistic model of how results are shaped.

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 dense but not bloated: the first sentence gives the operational core, and the second sentence is a substantive addition about result distribution. The middle clause is long, but every phrase carries useful signal.

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, idempotent tool with no required parameters and complete schema descriptions, the description covers the key decision that affects output shape. A short nod to alternatives such as search_signals or scope_signals would make it fully complete.

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?

All 4 parameters are already well described in the schema, so the baseline is 3. The description adds real semantic value for collection, explaining that omitting it produces a diversified all-collections view while passing it yields full-depth results.

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 opening sentence states a specific action — fetch the most recent live signals from the wire — and adds the format and filtering dimension. It is clearly distinguished from single-signal getters like get_signal and from search_signals by emphasizing 'latest from the wire' and CWF format.

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 explicit guidance for when to pass collection: the all-collections view is intentionally diversified, while collection reads a single collection at full depth. It does not explicitly name alternatives to exclude, so it narrowly misses the top end of the scale.

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

All Pronto 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.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get_signal re-reads a known row, get_latest_signals fetches by time, scope_signals filters by facets, search_signals matches words, and get_related_signals follows links. The overlapping pairs like get_facet_manifest/list_facets and get_fused_signal/list_fusion_products are explicitly differentiated in their descriptions, so an agent should not confuse them.

Naming Consistency5/5

The naming follows a consistent snake_case verb_noun pattern: get_ for direct fetches, list_ for catalog-style enumeration, register_ for identity creation, and scope_/search_ for query actions. The slight difference between get_fused_signal and list_fusion_products is meaningful and the verbs remain predictable.

Tool Count5/5

Thirteen tools is well within the sweet spot and each one covers a distinct capability: live reads, lookup by id, lexical search, facet filtering, related signals, fused products, catalogues, plans, billing, and agent registration. There is no obvious padding or excessive fragmentation.

Completeness5/5

The surface fully covers the domain: discovering the vocabulary, selecting signals, searching, fetching by id, following relationships, computing derived products, listing sources, and checking billing/plans. The only gaps would be account claiming and credential rotation, but those are explicitly deferred to external parties, so they are not tool-set gaps.

Resources