Skip to main content
Glama

Reveal a masked brand

reveal_brand
Idempotent

Unmasks one brand from search_signals on the free plan: its name, domain, store and Ad Library link. Pass the masked row's ref. Spends one of the account's 10 reveals a month (they reset on the 1st; a brand already revealed is free) and needs a signed-in free account. A revealed brand stays unmasked in later searches, and lookup_brand on its domain shows the full brand detail. Paid plans already see every brand.

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": {
      "ref": "<ref>"
    },
    "name": "reveal_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe ref of a masked row from search_signals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true) by disclosing the cost model: one of 10 monthly reveals, reset on the 1st, and no charge for re-revealing. It also states the auth prerequisite (signed-in free account) and the lasting side effect (the brand stays unmasked in later searches).

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 action and the return fields, then packs quota, auth, persistence, and plan gating into compact clauses. Dense but every sentence carries a distinct constraint; only the parenthetical quota detail borders on parenthetical clutter.

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?

No output schema exists, yet the description names the returned fields, covers the charge and its reset, the auth requirement, idempotence for already-revealed brands, and the effect on later searches. Nothing material about calling this correctly is left unstated.

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% and there is only one parameter, so the schema already defines ref. The description still adds value by pinning down provenance — the ref must come from a masked row in search_signals — which the schema description only partially implies.

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?

States a concrete verb and resource ('Unmasks one brand from search_signals') and enumerates exactly what the caller gets back: name, domain, store, and Ad Library link. It is clearly distinct from search_signals (which surfaces masked rows) and lookup_brand (which requires a domain).

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?

Explicitly says to pass the masked row's ref, and rules out the tool for paid plans ('Paid plans already see every brand'). It also names the follow-on path — lookup_brand on the revealed domain — so the agent knows when this step suffices and when to chain.

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