microvix_list_accounts
Read-onlyIdempotent
Lista os portais Microvix conectados a este install — id, label.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No |
Microvix
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds that it returns id and label, providing further clarity on behavior. No contradictions.
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, front-loaded with the main action, and contains no redundant words. It is concise but could be more structured.
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 list tool with an optional parameter and no output schema, the description provides the output fields but omits parameter usage. This is adequate but leaves a gap.
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 sole parameter 'account' is not explained in the description. With 0% schema description coverage, the description should clarify its purpose (e.g., filtering), but it does not.
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 it lists Microvix portals connected to the install, with id and label. This distinguishes it from sibling tools like microvix_clientes_fornec or microvix_produtos.
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 microvix_clientes_fornec or other listing tools. It simply states what it does.
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
B3.4/5.0
Disambiguation4/5
Tools are mostly distinct: platform utilities (authenticate, connect, marketplace) have clear separate roles, and microvix_* tools each target a different entity (clientes, lojas, movimento, pedidos, produtos variants, etc.). However, the marketplace tool has multiple sub-functions (search, describe, invoke, install) that could blur boundaries, but its description is thorough enough to prevent confusion.
Naming Consistency5/5
All tools use consistent snake_case naming. Platform tools are short descriptive words (authenticate, connect, marketplace), while domain-specific tools all follow the 'microvix_entity' pattern (e.g., microvix_clientes_fornec, microvix_produtos). No mixing of conventions or inconsistent verb styles.
Tool Count4/5
With 16 tools, the server is slightly above the ideal range (3-15) but still well-scoped. The platform utilities (6 tools) are necessary for authentication, marketplace interaction, and status; the 10 microvix-* tools cover the core domain tables without bloating. The count is reasonable for a server that combines platform and data query capabilities.
Completeness3/5
The microvix domain tools provide comprehensive read access to key entities (clientes, lojas, movimento, pedidos, produtos, inventário, vendedores), but there are no write/update tools (e.g., create_cliente, update_produto). For a data query server this may be acceptable, but the absence of CRUD operations is a notable gap if the purpose is to manage Microvix data fully.