Skip to main content
Glama

Brawl Stars

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses significant behavioral details beyond annotations: it fans out to SEC EDGAR, GDELT/GNews fallback, USPTO with PatentsView sunset soft-fail, and returns structured changes[] with citation URIs. These add useful context that annotations (readOnly, openWorld, idempotent) do not cover, making the tool's runtime behavior transparent.

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 information-dense, front-loaded with the core purpose, and each segment adds relevant detail (sources, fallbacks, formats, output). While it is one long sentence with many clauses, it avoids fluff and earns its length, but could be slightly better structured for scanning.

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, so the description appropriately explains what the tool returns ('structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs'). It also covers edge cases like GDELT preference, GNews fallback, and USPTO soft-fail, making it complete for a multi-source 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% for all three parameters, so the schema already explains them well. The description adds value by providing concrete examples for 'since' ('7d', '30d', '3m', '1y') and clarifying that 'value' can be a ticker or CIK. This is helpful beyond the schema descriptions, though not heavily necessary given the high coverage.

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 the tool provides a change feed for a company over a time window, with concrete examples like 'What's new with X' and 'updates on Acme'. It also distinguishes itself from the sibling tool entity_profile by explicitly stating when to use that instead, fulfilling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: use for recent changes/news/filings, and explicitly directs to entity_profile when the static profile is needed. This clearly delineates when to use this tool versus an alternative, satisfying the dimension.

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

All Brawl Stars 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

C2.9/5.0
Disambiguation2/5

The set mixes a general data-querying platform (Pipeworx) with a small Brawl Stars API wrapper. Within the Pipeworx cluster, ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim have overlapping lookup behavior, and the five polymarket_* tools cover similar prediction-market ground. The Brawl Stars tools are distinct but dwarfed, making the overall purpose confusing.

Naming Consistency3/5

Most Pipeworx tools use snake_case verb_noun patterns (ask_pipeworx, validate_claim, list_subscriptions), but Brawl Stars tools are bare nouns (brawler, club, player) and memory tools are bare verbs (remember, recall, forget). Some names are compound (generate_llms_txt, scan_competitor_ai_presence). No consistent pattern spans the whole set, though each subset is internally coherent.

Tool Count2/5

41 tools is far beyond what a Brawl Stars server needs; only about 10 are Brawl Stars-related. The bulk is a general-purpose data and prediction-market toolkit that seems bolted on. The count is not well-scoped to the server's declared name and purpose.

Completeness2/5

For Brawl Stars, the surface is thin: player and club profiles exist but there is no player search, club search, brawler-specific per-player stats, or detailed leaderboards. The Pipeworx side has broad coverage but is unrelated to the server name, so the domain is muddled and obvious Brawl Stars endpoints are missing.

Resources