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

Signal Feed API: market regime for agents

get_schema

Returns the closed JSON Schema for one issue, so agents can parse or validate issue payloads safely before relying on them.

Instructions

Free. Use when you must parse or validate an issue safely: the closed JSON Schema of one issue.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful traits beyond the schema: the call is free, and the returned schema is "closed" (i.e., fixed and authoritative for validation). It does not confirm read-only behavior, auth requirements, or rate limits, leaving the safety profile only partially covered.

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?

A single compact sentence with the usage condition up front and the return value trailing. The "Free." opener is a fragment that reads awkwardly but costs only a word, and nothing else is wasted.

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-parameter tool with an output schema, the description needs only to say what is returned and when to reach for it, and it does both. Only the missing read-only/auth framing keeps it from fully closing the gap left by absent annotations.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter language is present.

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 closed JSON Schema of one issue" names a specific resource (JSON Schema) and scope (one issue), which implicitly distinguishes it from list_issues and get_latest_issue. It is clear but never explicitly contrasts itself with those siblings, and the leading "Free." fragment adds noise rather than purpose.

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?

"Use when you must parse or validate an issue safely" gives a concrete triggering condition, which is more than most definitions offer. It stops short of naming when-not-to-use or pointing to an alternative sibling for related needs.

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