Skip to main content
Glama

get_facts

Weighted facts about what wins, each with its sample and its odds: e.g. 'in weight loss, EU, same brand and same launch day, video reached more people than image in 28 of 40 brands (70%, 95% interval 55-82%, p = 0.017)'. Use it when the user asks what is proven, what works better, video or image, or wants evidence rather than examples. Only facts that pass today are returned (30+ brands, p < 0.05, interval excluding 50%), with n, share, interval, p, method, read dates, caveats (always repeat them with the fact) and the commit of the code that computed them. Free.

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

Input Schema

NameRequiredDescriptionDefault
nicheNoe.g. weight loss
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting: it states the inclusion threshold (30+ brands, p < 0.05, interval excluding 50%), which today's facts are returned, the full return payload (n, share, interval, p, method, read dates, caveats, code commit), that caveats must be repeated, and that the tool is free. It doesn't say how many facts come back, whether they are ordered, or what is returned when nothing passes.

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?

Front-loads the purpose, then the example, then the usage, then the guarantees and payload. The example sentence is long but earns its place by showing output format, thresholds and caveats in one shot; otherwise little 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?

Without an output schema or annotations, the description still covers return fields, filtering guarantees, cost, and the caveat-handling obligation that would otherwise be invisible. It leaves only secondary operational gaps (result count, ordering, empty-result behaviour) for a tool with two optional filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the schema shows the niche example and the region enum, and the description's example ("in weight loss, EU") incidentally illustrates both filter values. However, it never says whether niche and region are optional narrowing filters or what happens when they are omitted, so no real meaning is added beyond the schema.

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?

The description names a specific resource with a concrete characteristic ("weighted facts about what wins") and disambiguates from neighbouring tools by contrasting evidence with examples ("wants evidence rather than examples"). The embedded example makes the shape of the result unmistakable.

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?

Gives explicit trigger conditions: the user asks what is proven, asks what works better (video vs image), or wants evidence rather than examples. That covers practical context, but it lists no exclusions and names no sibling tool to prefer when the user actually wants raw examples.

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