Skip to main content
Glama

MM7 Company MCP

check_1c_product_by_reg

Check a 1C product by registration number: whether the number is known and a short ITS contract summary. Same API as «Check product» on mm7.ru.

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": {
      "reg_number": "<reg_number>"
    },
    "name": "check_1c_product_by_reg"
  }
}

Input Schema

NameRequiredDescriptionDefault
reg_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations, so the description carries the burden; it does disclose that the result is an existence check plus a contract summary, which implies a read-only lookup. However it omits anything about authentication, error behavior for unknown numbers, or rate limits, so the behavioral picture is only partially filled in.

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

Conciseness3/5

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

Two sentences with no padding and the core purpose front-loaded. The trailing 'Same API as «Check product» on mm7.ru' is weakly earned context that occasionally reads as external reference noise rather than actionable guidance and could be trimmed without loss.

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?

An output schema exists, so the return format need not be spelled out, and complexity is low (one required param). Still, with no annotations and no routing among 22 siblings, the description leaves an agent guessing about when this is the right tool and what makes a reg_number valid.

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?

Schema coverage is 0%, so the description must compensate; it does clarify that reg_number is a 1C product registration number. That is meaningful but minimal — no format, source, or validity constraints for the single parameter are given.

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?

Specific verb+resource+identifier: 'Check a 1C product by registration number' and it states what the call yields (whether the number is known, plus a short ITS contract summary). It is distinguishable from most siblings, though it never names a competing tool like check_its_subscription or list_its_products.

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?

Usage is implied by the check-style purpose and the 'Same API as «Check product» on mm7.ru' reference, which hints at the source use case. But there is no explicit when/when-not guidance, no precondition on when to prefer this over check_its_subscription or get_contract_status with 22 siblings available.

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