billz_mcp

billz_get_brands

Retrieve a paginated list of product brands with optional search by name. Use to browse or filter brands for retail operations.

Instructions

Get list of product brands

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "billz_get_brands"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 27, 2026

TDQS

C2.1/5.0

Behavior1/5

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It fails to mention pagination behavior, sorting, authentication requirements, rate limits, or any side effects. The description is minimal and leaves the agent guessing about the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one sentence, but this brevity comes at the cost of essential details. It is under-specified for a tool with three parameters and no annotations. Conciseness should not sacrifice completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has three optional parameters, no output schema, and no annotations, the description is grossly inadequate. It provides no context for filtering, pagination, or expected result format. The agent cannot reliably use this tool based solely on the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate by explaining parameter purpose. It does not mention page, limit, or search. The description adds no value beyond the schema structure, leaving the agent without guidance on parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get list of product brands' clearly states the verb and resource. It distinguishes from sibling tools like billz_get_categories and billz_get_shops, as brands are a distinct entity. However, it lacks any additional context about what constitutes a brand.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There are no exclusions or context signals to help the agent decide. The description does not mention typical use cases or prerequisites.

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

Deploy Server