Skip to main content
Glama
Signal Feed API: market regime for agents

Signal Feed API: market regime for agents

list_issues

List every published issue date with its SHA-256 payload hash to confirm which issues exist or verify one you hold in an append-only ledger.

Instructions

Free. Use to see which issue dates exist or to verify an issue you hold: every published date with its payload SHA-256, append-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add real behavioral facts: it is free (no cost/quota concern), the data is append-only (so previously listed entries do not mutate), and each entry carries a SHA-256 for verification, implying a read-only, integrity-checkable listing. It omits ordering and pagination/size behavior, which for an unfiltered enumeration is a meaningful remaining gap.

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?

Compact and front-loaded: purpose and use cases come before the qualifying detail. The leading 'Free.' is a single-word cost signal that earns its place, though the colon-appended 'append-only' fragment reads slightly compressed.

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 zero-argument listing tool with a rich output schema, the description supplies enough to call it correctly and interpret results (dates plus hashes, immutable set). Only ordering/pagination expectations and sibling differentiation are left unstated, which keeps it short of full completeness.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The enumeration scope ('every published date') is consistent with the empty schema.

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 states the resource concretely: 'every published date with its payload SHA-256,' making clear this enumerates issue dates rather than issue contents. It never names how it differs from near-neighbors like get_latest_issue or get_catalog, so an agent must infer the distinction from the enumeration wording alone.

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?

Two explicit use cases are given: discovering which issue dates exist, and verifying an issue you already hold. There is no exclusion guidance (e.g., 'use get_latest_issue instead if you only need the newest'), so the agent gets context but no routing rules against siblings.

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