Skip to main content
Glama

signals_delta

Delta feed: returns assets changed after a caller-supplied Unix timestamp. Caller holds the cursor; server is stateless. Advance since from next_cursor.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoUnix seconds; 0 for initial call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it does disclose the two most important traits — statelessness and caller-held cursor — and implies a `next_cursor` return field. It does not state whether creations/deletions are included in 'changed', ordering, page-size limits, or the shape of returned assets, which leaves real gaps for a feed tool.

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?

Three short sentences, front-loaded with the core identity and followed by the two operational facts that matter. No filler or restated metadata.

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 single-optional-parameter feed with no output schema, the description covers the essential calling pattern including initialization and advancement. Only the returned asset shape and change-type semantics are left unspecified, which is a modest gap given the tool's simplicity.

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% and the schema already explains that `since` is Unix seconds with 0 for the initial call. The description adds genuine meaning beyond that by tying the parameter to the `next_cursor` feedback loop, telling the agent how successive values are derived.

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 opens with a specific verb+resource+scope: a delta feed returning assets changed after a supplied Unix timestamp. That distinguishes it implicitly from a full-listing sibling such as list_active_signals, though no sibling is named explicitly.

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 gives concrete when/how guidance for the paging loop: the caller holds the cursor, the server is stateless, and the next call should set `since` to the returned `next_cursor`. It stops short of naming alternatives or exclusions (e.g., when to use list_active_signals instead).

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