Skip to main content
Glama

agentdata-nl

by io.github.DarthSander

relay_reddit_search

Keyword-search all of Reddit (or one subreddit) for $0.05 per call — social listening for AI agents without login or API key. Returns matching posts with title, author, subreddit, score, comment count, permalink and timestamp, sorted by relevance, top, new, hot or comments, with an optional time window. Track brand mentions, monitor topics, surface community sentiment. Relayed live from a proven upstream source; if the source is down you get a 503 and pay nothing. Pay per call in USDC on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesKeyword or phrase to search; wrap a multi-word phrase in double quotes for exact match
sortNoResult ranking (default relevance)
timeNoTime window — applies to sort=top
limitNoMaximum posts to return (1-100)
subredditNoOptional — scope the search to this subreddit (r/ prefix optional); omit for a sitewide search

TDQS

A4.5/5.0
Behavior5/5

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

Since no annotations are provided, the description fully covers behavioral traits: it returns specific fields, allows sorting and time filtering, mentions pay-per-call cost and pay-in-ins, and explains failure mode (503 with no charge). No contradictions with annotations.

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?

The description is front-loaded with the core action and cost, then efficiently covers parameters, use cases, and failure behavior. While not minimal, every sentence adds value and avoids redundancy.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is fairly complete. It covers output fields, sorting, time window, pricing, and failure mode. It lacks explicit pagination or rate limit info but is adequate for a 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?

The input schema already provides 100% coverage of parameters. The description adds extra value by specifying exact match syntax for 'q', clarifying that 'time' applies to 'sort=top', and noting the optional subreddit scope. This goes beyond the schema's baseline.

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 clearly states that the tool performs keyword searches on Reddit or specific subreddits, returning specific post fields. It distinguishes itself from siblings like web_search by focusing exclusively on Reddit.

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?

The description provides clear use cases (social listening, brand monitoring) and conditions (no login/API key required, pay per call). However, it does not explicitly state when to avoid this tool or compare to siblings like web_search.

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

All agentdata-nl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool targets a distinct action and domain: country-specific company checks (check_ch_company, check_fr_company, etc.), insolvency checks, crypto signals, x402 network tools, etc. Descriptions are detailed and make boundaries clear, with no two tools appearing to do the same thing.

Naming Consistency5/5

Tool names follow very consistent patterns: 'check_<country>_<entity>' for registers, 'crypto_*' for crypto intelligence, 'x402_*' for x402 network functions, 'screen_*' for screening, and a few free-form names like 'verify_eu_vat' and 'lookup_lei' that still fit the verb_noun style. No mixing of conventions.

Tool Count4/5

39 tools is high but justified by the broad scope: the server aggregates many country-specific checks, insolvency registers, crypto tools, x402 monitoring, and auxiliary functions (like phone number buying, LEI lookup). Each tool serves a clear purpose, and the count is not excessive given the coverage. A slight reduction could be possible by merging some country checks, but overall it's reasonable.

Completeness4/5

The server covers major European company registers (CH, UK, FR, NL, NO, PL, CZ, FI), insolvency checks (NL, FR), sanctions screening, VAT validation, crypto market intelligence, and x402 network tools. It acknowledges gaps (e.g., no German check) and provides fallback tools like 'screen_eu_supplier' and 'file_agent_want'. Minor missing pieces (e.g., Italian company check) keep it from a perfect 5.

Resources