Skip to main content
Glama

Search signals

search_signals
Read-only

Search the scored RWA / tokenization / family-office signal feed. All filters are optional and combine with AND. Returns signals with intent score (0–100), tier, region, entity, summary and source URL, plus total_matching.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against title, summary, entity name and tags.
sortNoDefault: intent (highest score first).
tierNoIntent tier.
typeNoSignal type.
limitNoDefault 20.
regionNoRegion code: CH, EU, UK, US, APAC, MENA or Global. Country names like 'Switzerland' are accepted.
min_scoreNoMinimum intent score.
since_daysNoOnly signals published in the last N days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower; the description still adds value by listing the returned fields (intent score 0–100, tier, region, entity, summary, source URL) and total_matching, which compensates for the absent output schema. It does not mention pagination behavior beyond the limit parameter, truncation, or empty-result handling.

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 sentences, front-loaded with the resource, then filter semantics, then return shape. No filler, no restatement of the title, and every clause carries information an agent needs before calling.

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?

With 8 optional params, 100% schema coverage, and no output schema, the description covers what is missing: the return payload and the AND-combination rule. It stops short of explaining how sort interacts with limit or what an empty feed looks like, which are minor for a read-only search 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, but the description adds genuine cross-parameter meaning: all filters are optional and combine with AND, which the per-parameter schema entries do not state. Score semantics (0–100) are reinforced rather than contradicted, and no parameter behavior is misdescribed.

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?

States a specific verb and a specific resource: 'Search the scored RWA / tokenization / family-office signal feed', with the domain scope and the returned fields spelled out. It does not, however, distinguish itself from the sibling get_signal_brief, so an agent has to infer the boundary between 'search' and 'brief'.

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?

The description says all filters are optional and combine with AND, which is real usage guidance for query construction. It offers no when-to-use context, no when-not-to-use, and no pointer to the sibling tool for the full-brief case.

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