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

Signal Feed API: market regime for agents

get_disclosures

Check a seller’s conflicts of interest—personal positions, affiliate commissions, and other biases—before relying on their market signal.

Instructions

Free. Use to check the seller's conflicts of interest: personal positions, affiliate commissions and other conflicts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call is free and what category of data is returned, but says nothing about authentication requirements, whether the data is cached or live, or how large the response may be. The zero-parameter get shape makes read-only semantics self-evident, which limits the severity of the 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?

Two short sentences with no filler; the cost note is front-loaded and the purpose follows immediately. The phrase "and other conflicts" is slightly vague but adds scope rather than redundancy.

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?

The tool is trivial to invoke (zero parameters) and an output schema exists, so return values need not be explained. The description says enough about what the data covers; the only real gap is that it never explains how the seller in question is determined given there is no seller parameter.

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 no parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly implies the call needs no input to identify a seller, which 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 gives a specific verb (check) and resource (the seller's conflicts of interest), then enumerates the content: personal positions, affiliate commissions, and other conflicts. That content-level detail distinguishes it well from siblings like get_deviations or get_catalog, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to check the seller's conflicts of interest" implies the situation in which to call it, and "Free" signals it costs nothing to call. There is no guidance on when not to use it, no named alternative, and no note on whether a prior context (e.g., a selected seller) is required.

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