BuyWise

Check brands

check_brands

Read-onlyIdempotent

Use this when the user asks whether a brand is reputable or what kind of brand it is (an established name, a store's own label, an independent maker, or a generic white-label name), or wants brands compared while shopping. Returns findings on each brand: what kind of brand it is, its reputation for quality and its usual price tier, each with a confidence. Signals only, never a buy or avoid verdict. Does not browse the web and is not for banking, health or email pages. Pass brand names as the user or the listing gave them, up to 50 per call.

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": {
      "brands": "<brands>"
    },
    "name": "check_brands"
  }
}

Input Schema

Name	Required	Description	Default
`brands`	Yes	Brand names, 1-50.
`detail`	No	Include each finding's full probability distribution. Default false.

Output Schema

Name	Required	Description	Default
`quota`	No	What is left of the allowance after this request.
`brands`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld=false, so safety is covered. The description still adds valuable substance: what each finding contains, that confidence is attached, that these are 'signals only, never a buy or avoid verdict', and importantly 'does not browse the web' — clarifying the openWorldHint=false meaning. Good added context.

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?

Four sentences, front-loaded with the trigger condition, then returns, then exclusions, then parameter guidance. Dense but every sentence earns its place; the enumeration of brand types is slightly verbose but aids selection.

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?

Output schema exists, so return details need not be explained, and the description nonetheless summarizes the finding shape. Given annotations plus output schema, nothing an agent needs to invoke this correctly is missing.

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 the baseline is 3. The description adds a genuine constraint not obvious from the schema alone: 'Pass brand names as the user or the listing gave them, up to 50 per call' — coaching formatting and echoing the 50 cap, which exceeds schema-only value.

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 specific verb+resource ('Check brands') and enumerates what 'kind of brand' means (established name, store's own label, independent maker, generic white-label), distinguishing it from check_product/check_products which operate on products. An agent can select it confidently.

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?

Explicit when-to-use ('when the user asks whether a brand is reputable or what kind of brand it is... or wants brands compared while shopping') plus explicit when-not ('not for banking, health or email pages'). This is unusually thorough routing guidance.

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

All BuyWise 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?