mindbox-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.2.0
Disambiguation5/5
Each tool targets a distinct function: customer profile retrieval/update, order creation, segments lookup, product list, and a raw operation escape hatch. No two tools seem to overlap, and the dangerous run_operation is clearly separated by its warning.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern (get_customer, create_order, get_segments, get_product_list, update_customer, run_operation). This is predictable and easy for an agent to parse.
Tool Count5/5
With 6 tools, the set is well-scoped for a CRM/ecommerce integration. It covers core customer and order operations without unnecessary bloat, making it easy to navigate.
Completeness4/5
The set covers customer retrieval/update, order creation, segments, and products, but lacks explicit order retrieval or listing, and there is no direct customer creation. However, the run_operation tool provides a raw API fallback, mitigating some gaps, though it introduces risk.
Average 3.2/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 3 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool retrieves a product list, without revealing any side effects, authentication requirements, rate limits, or return format. Since it's a read operation it's likely benign, but the description fails to explicitly confirm it's non-mutating or describe any pagination behavior beyond what the schema implies. This is a significant gap given no annotation support.
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, concise sentence that front-loads the core purpose. There is zero wasted text or unnecessary elaboration. It's appropriately minimal for a straightforward list operation and ranks highly for conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that this tool has 3 parameters, all with defaults, and no output schema, the description should provide more context about behavior and usage. It doesn't explain the meaning of the 'operation' parameter or how pagination works (though the schema covers that). It also doesn't mention what the response looks like or any prerequisites. For a simple read operation, it might be acceptable, but the lack of any additional context beyond the schema makes it incomplete for an agent that needs to call it correctly without prior knowledge.
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 description coverage is 100%, and each parameter (page, operation, page_size) already has a clear description and default value. The tool description adds no additional meaning beyond the schema, but the schema itself is sufficient. Baseline of 3 is appropriate since the description doesn't enhance parameter understanding, but also doesn't need to because the schema is comprehensive.
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 clearly states the tool retrieves a list of products from Mindbox, using a specific verb ('Получение' = getting) and resource ('список товаров' = product list). It distinguishes from siblings like get_customer and get_segments by referencing a different entity type, though it doesn't explicitly compare to a potential get_products alternative. Clear enough for an agent to understand the core purpose.
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?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention use cases, exclusions, or how it relates to sibling tools like run_operation or create_order. An agent is left to infer usage from the name and schema, which is insufficient for making correct tool selection decisions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden. The verb 'Получение' implies a read operation, but it does not explicitly state that it does not modify data, nor does it mention any other behaviors like pagination or permission requirements. This is a significant gap for a tool with no annotation coverage.
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?
The description is a single short sentence, concise and front-loaded. It states the core action and object without fluff, earning its place with minimal waste, though it could arguably be too minimal for a complex tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 4 optional parameters, no output schema, and no annotations, the description is insufficient for an agent to confidently invoke it correctly. It lacks information about when to use it, what the response looks like, and any behavioral caveats. The schema covers parameter semantics, but the overall context is thin.
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 schema description coverage is 100%, providing descriptions for all four parameters. The tool description adds no extra meaning beyond the schema, so it meets the baseline of 3 without needing to compensate for missing schema information.
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 states a clear verb ('Получение' = getting) and resource ('сегментов клиента' = customer segments), which is distinct from sibling tools like get_customer. However, it does not elaborate on the scope or specifics of segments, so it is clear but not highly differentiating.
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?
The description provides no guidance on when to use this tool versus alternatives such as get_customer or run_operation. There is no mention of prerequisites, use cases, or exclusions, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description bears the full burden of disclosing behavioral traits. It only states that it updates a profile, without specifying whether it is a partial or full update, what happens on non-existent customers, authentication or permission requirements, or any side effects. For a mutation tool this is insufficient, leaving the agent to guess critical behavior.
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?
The description is a single sentence with no redundant words, making it concise and appropriately front-loaded with the core purpose. However, given the tool's complexity (8 parameters, nested object), one could argue it is under-specified, but that is more a completeness issue than a conciseness problem. The text itself is efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 8 parameters, a nested object, no output schema, and no annotations, the description must provide substantial context to be usable. It fails to mention how to identify the customer, whether any fields are required (none are marked required but logically an identifier is needed), the relationship to run_operation, or the expected response. This is far from complete for a tool of this complexity.
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 schema provides descriptions for all 8 parameters, so coverage is 100%, justifying the baseline of 3. The description adds no additional meaning about parameters, such as how to identify the customer or which fields are expected together. Since the schema already covers basic semantics, the description does not need to compensate, but it also does not enrich understanding of parameter relationships.
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 states the verb 'Обновление' (update) and the resource 'профиль клиента' (customer profile) within 'Mindbox', making the core purpose clear. It is distinguishable from sibling get_customer (read) and create_order (different resource), though it does not explicitly differentiate itself from run_operation which could also update. The single-sentence description gives enough to know what it does, but lacks any elaboration on scope.
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 is no mention of prerequisites (e.g., the need for an identifier like external_id or email), nor any exclusion criteria. The agent must infer from the name and sibling tools. This is a clear gap for a tool that overlaps conceptually with get_customer and run_operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention side effects, authorization requirements, reversibility, or impact on customer data—important for a creation tool with client binding.
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?
The description is a single, focused sentence with no fluff. It is appropriately concise and front-loaded with the primary purpose, but it is slightly under-specified for a complex tool—though that is more relevant to contextual completeness than conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 7 parameters, 3 required, no annotations, and no output schema, the description is too sparse. It does not explain how customer binding works, what constitutes a valid order, or any constraints or prerequisites. An agent would lack critical context to use it correctly.
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 100% and every parameter has a description. The tool description adds no parameter-level detail, which is acceptable per the baseline. However, it doesn't synthesize how parameters relate (e.g., which customer fields are optional vs. required for binding), leaving some semantic gaps that the schema alone already mostly fills.
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 clearly states the action (creating an order) and the resource (order in Mindbox), plus the distinguishing detail of binding to a customer. This distinguishes it from sibling tools like get_customer or update_customer, which operate on different resources.
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 versus alternatives. There is no mention of conditions for choosing create_order over run_operation or update_customer, nor any exclusions. The description is purely declarative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'getting', which hints at a read operation, but does not mention possible side effects, authentication requirements, rate limits, error behavior, or what happens when multiple identifiers are provided. The bare action leaves significant behavior undocumented.
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?
A single, front-loaded sentence that states the primary action and keys without any filler. It is concise 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 retrieval tool with moderate parameter count and no output schema, the description covers the core purpose but omits practical details such as whether at least one identifier is required, how identifiers combine, or expected response format. The schema fills in some gaps (e.g., operation matching), but the description provides no extra context beyond the basic action.
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 description coverage is 100%, so all four parameters (email, phone, operation, external_id) already have descriptions in the schema. The tool description adds no parameter-specific guidance beyond naming the identifiers, and it does not clarify precedence, mutual exclusivity, or the requirement to match the operation name to project configuration (though the schema does state that). Baseline 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 clearly states the verb 'get' and the resource 'customer profile from Mindbox', and explicitly mentions the search keys (email, phone, ID). This distinguishes it from siblings like get_segments or get_product_list, which target different resources.
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 the tool is used to retrieve customer data by one of the listed identifiers, but it does not provide explicit when-to-use guidance or contrast with alternatives (e.g., 'use get_segments for segments, not customers'). No exclusions or context that would help an agent decide between tools are included.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it is dangerous, may modify data, runs under a secret key, and can be disabled via an environment variable. This exceeds typical descriptions by highlighting side effects and safety mechanisms. However, it does not describe return behavior or error cases, which are inherently variable for arbitrary operations.
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, short sentence that immediately conveys the danger and purpose. It is front-loaded with the warning and efficiently states both the capability and the safety toggle. No redundancy or filler.
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 an arbitrary-operation tool with no output schema and no annotations, the description covers the risk profile but omits practical guidance like how to discover operation names, what the response format looks like, or typical use cases. Given the tool's open-ended nature, some guidance would be helpful for safe invocation, but the minimal description is partially acceptable because the behavior depends entirely on the called operation.
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 schema already provides descriptions for all three parameters (operation, body, mode) with 100% coverage. The description adds no additional semantic detail beyond the schema. It does not explain how to reference operation names or provide examples. Since coverage is high, the baseline 3 is appropriate; the description does not compensate for any gaps.
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 clearly states that this tool executes an arbitrary Mindbox API operation ('выполнение ПРОИЗВОЛЬНОЙ операции Mindbox API'), which distinguishes it from the specific sibling tools like get_customer or create_order. It uses a generic verb 'run' but the arbitrariness is explicit. It doesn't specify a particular resource, but for a raw-operation tool that's appropriate.
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 this is for operations not covered by dedicated tools (since it's arbitrary and warns of danger), and mentions a safety toggle (MINDBOX_ALLOW_RAW). However, it does not explicitly state 'use this when no other tool fits' or provide alternatives. The warning signals caution, but when-to-use versus when-not-to-use is only implied, not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mindbox-mcp MCP server](https://glama.ai/mcp/servers/theYahia/mindbox-mcp/badges/card.svg)](https://glama.ai/mcp/servers/theYahia/mindbox-mcp)

Score Badge

Copy to your README.md:

[![mindbox-mcp MCP server](https://glama.ai/mcp/servers/theYahia/mindbox-mcp/badges/score.svg)](https://glama.ai/mcp/servers/theYahia/mindbox-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theYahia/mindbox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server