Skip to main content
Glama

Market signals

market_signals
Read-onlyIdempotent

Use when asked about the cannabis market or industry figures. Facts from cannabis industry news in our own words, each with its number, the data source the article names (or "no source named") and a link to the publisher. Market context, not medical evidence. Newest article first; replaced figures are left out unless asked for. Example arguments: {"limit":5}.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items to return, at most 50.
sinceNoA day, YYYY-MM-DD: only signals from articles on or after it.
regionNoOnly signals of this region, for example "de" or "eu".
include_replacedNoTrue to include figures a newer signal replaced (history).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is return-shape and semantics, which it does well: per-item number, the source the article names or 'no source named', a publisher link, newest-article-first ordering, and suppression of replaced figures unless requested. That last clause directly explains the include_replaced default behavior, which annotations cannot convey.

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?

Four short sentences, front-loaded with the usage trigger, then content shape, then scope exclusion, then ordering/default behavior. Nothing is repeated from the schema and no sentence is filler; even the example arguments sentence is compact and illustrative.

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?

There is no output schema, and the description compensates by enumerating the fields of each returned signal and its ordering, which is exactly what an agent needs to consume results. Parameters are fully covered by the schema, and scope boundaries versus medical evidence are stated, leaving no material gap for calling this tool correctly.

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 schema already carries parameter documentation and the baseline is 3. The description adds real meaning on top: it clarifies that replaced figures are excluded by default (the include_replaced semantics) and reinforces ordering as newest-first, plus a worked example with {"limit":5}.

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 domain and content precisely: facts from cannabis industry news, each with a figure, named source, and publisher link. It also explicitly distinguishes itself from medical/clinical siblings with 'Market context, not medical evidence.' The retrieval verb itself is only implied ('Facts from...' rather than 'lists/returns'), which keeps it just short of a 5.

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 asked about the cannabis market or industry figures' gives a concrete trigger condition, and 'Market context, not medical evidence' functions as an explicit when-not rule that steers agents away for clinical questions. It doesn't name a specific sibling to use instead for the medical case, so it stops at 4.

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.