Skip to main content
Glama

Brawl Stars

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations: memory is scoped by identifier, authenticated users get persistent memory, anonymous sessions retain for 24 hours, and it pairs with recall/forget. This enriches the idempotentHint and destructiveHint already provided, offering retention and scoping specifics not present in structured data.

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?

The description is three sentences long, front-loads the purpose, and each sentence earns its place: purpose/usage, storage mechanics, and pairing with sibling tools. No filler or repetition.

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?

For a simple two-parameter memory store with no output schema, the description covers purpose, usage context, persistence behavior, and integration with recall and forget. It is complete for the tool's complexity.

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 100%, so the input schema already fully documents key and value. The description reinforces the key-value concept and gives practical examples, but it does not add new semantics beyond the schema. Per baseline rules, a 3 is appropriate when the schema carries the descriptive load.

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 opens with a specific verb and resource: 'Save data the agent will need to reuse later — across this conversation or across sessions.' This clearly states what the tool does and distinguishes it from sibling tools like recall and forget by explicitly naming them as counterparts.

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 when-to-use guidance: 'Use when you discover something worth carrying forward... so you don't have to look it up again.' It mentions alternatives (recall, forget) but does not explicitly contrast with them or state when not to use this tool. Thus, it has clear context but lacks explicit exclusions.

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