install_blocks_cli
Install Blocks CLI using npm.
Returns: JSON string with installation result
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
l0-py-blocks-mcp
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It only notes that a JSON string with installation result is returned. It does not disclose prerequisites like Node.js/npm availability, whether the installation is global or local, idempotency, or potential side effects such as modifying global packages. This is minimal disclosure.
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 two short sentences, front-loaded with the core action. Every word earns its place; no redundant information 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?
Given the tool has no parameters and an output schema exists, the description's mention of the return format is adequate at a basic level. However, it lacks context about installation prerequisites, potential impacts, and when to use this instead of check_blocks_cli. This is a minimal viable description but with clear gaps in operational context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so schema coverage is trivially 100%. There is nothing to add about parameter semantics, and the baseline of 4 for zero-parameter tools applies.
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 tool installs Blocks CLI using npm, with a specific verb and resource. It is distinct from the sibling tool check_blocks_cli, which presumably verifies installation rather than performing it.
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 explicit guidance on when to use this tool versus alternatives. Since check_blocks_cli exists as a sibling, the description could have mentioned using that to verify installation, but it doesn't. Usage is only implied by the tool's name and description.
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.
TDQS
A3.5/5.0
Disambiguation4/5
The tools are organized into clear domains (auth, roles, schemas, translations, projects), and within each domain, tools have distinct purposes (e.g., get_schema vs list_schemas, save_captcha_config vs update_captcha_status). A few pairs like get_auth_status and get_authentication_config could cause minor confusion, but their descriptions clarify the difference.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case, using predictable verbs like get, list, create, update, set, enable, and configure. Even longer names like save_module_keys_with_translations adhere to the same convention, with no mixed casing or arbitrary styles.
Tool Count2/5
With 36 tools, the server exceeds the typical well-scoped range for MCP servers. While the broad platform domain justifies some breadth, the sheer volume can overwhelm agents and suggests the toolset could be consolidated or split into smaller, focused servers.
Completeness3/5
The toolset provides decent coverage for creation, listing, and some updates across entities like permissions, roles, schemas, and translations. However, there are notable gaps: no delete operations for most resources, no role update, and no project update/delete, which leaves lifecycle management incomplete.