Skip to main content
Glama
Sign In

Pronto

by stream.pronto.api
OverviewDiscussionsAdmin

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.

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

Input 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.

  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

A3.6/5.0
Behavior4/5

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

The description discloses behavioral traits beyond the annotations: the all-collections view is diversified with provider/cap limits, overflow is named on a note line rather than dropped, and passing collection yields full depth. These details are not in the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) and meaningfully inform caller expectations about response composition and tradeoffs.

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 purpose is front-loaded in the first sentence, and the second paragraph explains important behavioral constraints. The prose is reasonably compact for the behavioral detail it conveys, though the second paragraph could be tightened without losing meaning.

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?

There is no output schema, so the description should compensate by explaining what the response looks like. It names 'CWF format' but does not expand the acronym or describe the line structure, pagination via META cursor beyond the schema, or error behavior. The diversification explanation helps, but gaps remain for an agent to fully predict the response shape.

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 coverage is 100%, so the baseline is 3. The description adds a small nuance for the collection parameter (full depth when passed) but says nothing about limit, cursor, or relate beyond what the schema already provides. The added value is marginal and confined to one parameter.

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 the tool fetches the most recent live signals from the wire in a specific token-efficient CWF format, optionally filtered by collection. This distinguishes it from sibling tools like get_signal (single signal), get_related_signals (related signals), and search_signals (search), while also conveying the unique all-collections diversification behavior.

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?

The description provides guidance on choosing between all collections vs. a single collection (full depth) but does not explicitly say when to use this tool versus its siblings. No alternative tools are named, and there is no when-not-to-use guidance, so the agent must infer selection criteria from tool names alone.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources