Skip to main content
Glama
Sign In
billz_mcp

billz_mcp

by asadbekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

billz_get_categories

Retrieve product categories from BILLZ POS. Filter by search, pagination, or deleted status for inventory management.

Instructions

Get product categories

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_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
searchNo
is_deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only implies read-only with 'Get', but does not confirm or describe any side effects, pagination, or filtering 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?

Extremely short at 3 words, but this is under-specification, not conciseness. For a tool with 4 optional parameters and no annotations, the description should include more details.

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 4 parameters, no output schema, and no annotations, the description is grossly inadequate. The agent lacks necessary information to invoke the tool correctly.

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?

The input schema has 4 parameters (page, limit, search, is_deleted) with 0% description coverage. The description does not mention any parameter meaning, leaving the agent without guidance on how to use them.

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

Purpose3/5

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

Description says 'Get product categories', which is a clear verb+resource. However, it does not distinguish from sibling tools like billz_get_brands, which similarly retrieve lists. More specificity would help.

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 on when to use this tool over alternatives. The description lacks context about scenarios or exclusions.

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

Deploy Server

Other Tools