tollbooth

research_pack

Legacy alias for osint_research_pack. Multi-source OSINT research pack — GDELT + BBC + HN + Reddit, 4-layer verification layer (existence+recency+multi-source+domain allowlist) + combined relevance scoring.

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": {
      "topic": "<topic>"
    },
    "name": "research_pack"
  }
}

Input Schema

Name	Required	Description
`topic`	Yes	Research topic query
`domains`	No	Optional domain filter allowlist
`hours_back`	No	Hours back, default 24
`include_sources`	No	Sources to include: gdelt, bbc, hn, reddit

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavioral detail: the four upstream sources, the existence+recency+multi-source+domain-allowlist verification layers, and relevance scoring. It omits anything about latency, external network calls, rate limits, result volume, or what the returned 'pack' looks like, which matters for a multi-source fan-out tool.

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 dense sentences with no filler, covering identity, sources, verification, and scoring. Leading with 'Legacy alias' before the capability is slightly backwards for an agent scanning for function, but the whole thing is short enough that it costs little.

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

Completeness3/5

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

Four parameters are fully documented in the schema, so input-side completeness is fine. However, with no output schema, the description is the only source of truth on what a 'research pack' returns, and it never describes the result structure, per-source vs. aggregated output, or truncation behavior.

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 baseline is 3, but the description adds genuine meaning by naming the concrete source set (GDELT, BBC, HN, Reddit) that the include_sources parameter enumerates and by tying the 'domain allowlist' verification layer to the domains parameter. That connects parameters to the pipeline rather than just restating field names.

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 names the operation concretely: a multi-source OSINT research pack composed of GDELT + BBC + HN + Reddit, with a 4-layer verification pipeline and combined relevance scoring. It also identifies itself as a legacy alias for the sibling osint_research_pack, which lets an agent distinguish the two. It does not spell out the output shape, but the resource and its composition are unambiguous.

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?

Calling it a 'legacy alias' implies the canonical osint_research_pack should be preferred, but the description never states that explicitly nor says when this alias would still be the right call (e.g., backwards compatibility). Usage is inferable rather than instructed.

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

All tollbooth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?