Skip to main content
Glama

Signal Lab: free data for trading and AI agents

Suggest a data source

suggest_source
Idempotent

Send us a free or open data source we do not list yet. It goes into a private queue and is checked like every listing (free access, terms, policy); nothing is published automatically and the URL is not visited by this server. Give the provider's own https page (no shorteners, IP addresses, paste or leak sites, malware hosts or dark-web links), its name, a domain from the list, and why it is useful in at most 280 characters. Optional handle (letters, digits, _ or -, at most 40) may be credited as plain text if the source is listed. Do not include personal information. Limit: 5 an hour per caller.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "name": "<name>",
      "domain": "<domain>",
      "reason": "<reason>"
    },
    "name": "suggest_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe provider's own https page for the data, for example its API docs
nameYesName of the source or provider
domainYesWhich kind of data it is
handleNoOptional credit handle: letters, digits, _ or -
reasonYesWhy it is useful, plain text, at most 280 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "Financial",
      -  "Global Macro",
      -  "Energy",
      -  "Agriculture & Food",
      -  "Money Flows",
      -  "Transport & Shipping",
      -  "Weather",
      -  "News & RSS",
      -  "OSINT",
      -  "Cyber Threat",
      -  "Other"
      -]New value: +[
      +  "Financial",
      +  "Global Macro",
      +  "Energy",
      +  "Agriculture & Food",
      +  "Money Flows",
      +  "Transport & Shipping",
      +  "Research & Grey Literature",
      +  "Weather",
      +  "News & RSS",
      +  "OSINT",
      +  "Cyber Threat",
      +  "Other"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "Financial",
      -  "Global Macro",
      -  "Energy",
      -  "Agriculture & Food",
      -  "Money Flows",
      -  "Transport & Shipping",
      -  "Weather",
      -  "News & RSS",
      -  "OSINT",
      -  "Cyber Threat",
      -  "Energy & Infrastructure",
      -  "Money Flows & Trade",
      -  "Other"
      -]New value: +[
      +  "Financial",
      +  "Global Macro",
      +  "Energy",
      +  "Agriculture & Food",
      +  "Money Flows",
      +  "Transport & Shipping",
      +  "Weather",
      +  "News & RSS",
      +  "OSINT",
      +  "Cyber Threat",
      +  "Other"
      +]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: nothing is published automatically, the URL is not visited by this server, review criteria are named (free access, terms, policy), personal information is prohibited, and a concrete rate limit of 5 per hour per caller is given. The idempotentHint is also made sensible by describing the submission as a queued, non-mutating action.

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 front-loaded sentences with zero filler: purpose, then submission/review behavior, then field requirements and limits. Every clause carries a constraint or an outcome the agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description explains the outcome (queued, reviewed, not published) and the credit condition, so the agent knows what it gets back. With rate limits, content restrictions, and privacy rules all stated, nothing material is missing for a 5-parameter write tool.

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%, so the baseline is 3; the description earns extra credit by adding eligibility rules the schema omits: the page must be the provider's own https page, and shorteners, IP addresses, paste/leak sites, malware hosts, and dark-web links are rejected. It also clarifies that the handle is credited as plain text only if the source is listed, and restates the 280-character reason limit with intent.

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?

Opens with a specific verb and resource: 'Send us a free or open data source we do not list yet.' This immediately distinguishes it from sibling tools like search_catalog, get_entry, and feedback, which read or act on existing listings rather than submitting new ones.

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?

Clearly states the condition for use ('a data source we do not list yet') and what happens next (private queue, reviewed like every listing). It does not explicitly route the agent to the `feedback` sibling for corrections or complaints, which is the main missing piece.

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