Bitrix24 MCP server

b24_read_product_catalog

Read the product catalog structure including sections, properties, prices, and units.

Instructions

Lee la estructura de configuración del catálogo de productos: secciones, propiedades, precios y unidades.

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": "b24_read_product_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`webhook_url`	No	URL del webhook (opcional si está configurado por defecto)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description clearly indicates a read operation ('Lee') but provides no additional behavioral context beyond that. Since no annotations are provided, the description carries the full burden; it doesn't mention response format, whether this is live data or cached configuration, or any access prerequisites. It is adequate but not rich.

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 a single, front-loaded sentence that wastes no words and clearly enumerates the contents of the catalog structure with a colon-separated list. It is compact and easy to scan.

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

Completeness3/5

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

For a simple read tool with zero required parameters, the description explains what the tool reads and the main components covered. However, there is no output schema and no mention of return format, pagination, or how this tool differs from b24_products_sections, so an agent may lack full context for evaluating the response.

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?

The only parameter is the optional webhook_url, and the schema describes it fully with 100% coverage. The description does not mention parameters, but because the schema already covers the parameter well, the baseline of 3 is appropriate.

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 uses a specific verb ('Lee') and identifies a clear resource: the configuration structure of the product catalog, listing sections, properties, prices, and units. This distinguishes it from product-data siblings like b24_products_list or b24_products_get, which focus on records rather than catalog configuration structure.

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

Usage Guidelines3/5

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

The description implies when to use the tool: when the agent needs catalog configuration structure rather than product data. However, it does not explicitly mention alternatives or state when not to use it, leaving the agent to infer the distinction from sibling tool names.

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