superlogica_unidades_post_update
Unidades: Editar uma unidade (PUT /unidades/post). [write, altera dados]
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| query | No | ||
| account | No |
Superlógica Condomínios
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly labels the operation as '[write, altera dados]', which discloses that this call mutates data, beyond what the annotations (all false hints) provide. However, it does not explain side effects, idempotency, required permissions, or reversibility, leaving a partial behavioral disclosure.
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 compact and front-loaded with the main action and resource. The endpoint and write tag are included without unnecessary padding, though the '[write, altera dados]' label is slightly redundant with 'Editar'.
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?
For an update operation with three undocumented string parameters and no output schema, this description is insufficient. It specifies the action and endpoint but leaves the request body, query, account, and response format entirely unspecified, so an agent cannot correctly construct a call.
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?
With 0% schema description coverage and no parameter details in the tool description, the three parameters (body, query, account) are completely unexplained. The agent cannot determine what fields the body should contain, how the query parameter is used, or what account refers to.
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 ('Editar uma unidade') and the resource ('unidade'), with the endpoint and an explicit write label. It distinguishes itself from sibling tools like superlogica_unidades_create, superlogica_unidades_list, and superlogica_unidades_delete by indicating this is specifically for editing an existing unit.
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 given about when to use this tool versus alternatives such as the create or delete unit tools. The word 'Editar' implies usage for existing units, but there are no explicit exclusions, prerequisites, or comparisons to siblings.
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
C2.5/5.0
Disambiguation2/5
Many tools have overlapping boundaries: arquivos_create vs arquivos_put both add files, configuracoes_list vs configuracoes_list_get vs ini_config are three config-listing variants, and sindicos_list vs sindicos_list_get vs responsaveis_list vs usuario_list are four person-listing tools with similar semantics. The recurring _list vs _list_get suffix pattern across resources (inadimplencia, planocontas, configuracoes, sindicos) makes selection genuinely ambiguous.
Naming Consistency2/5
The superlogica_<resource>_<action> prefix is consistent, but action verbs are a chaotic mix of English (create, delete, update) and Portuguese (desfazer, estornar, liquidar, desinvalidar), and HTTP-method suffixes are semantically inverted (malotes_put creates while malotes_post edits; despesas_post edits). Platform tools (authenticate, marketplace, toolkit_info) break the pattern entirely, and there is a typo in ocorrencias_susgestoes.
Tool Count1/5
120 tools is an extreme count, far beyond the 50+ threshold for a mismatch. Even granting the breadth of a condominium-management domain, the surface looks like an uncurated endpoint-by-endpoint dump of the entire Superlógica API rather than a designed tool set.
Completeness4/5
The core domain is remarkably well covered: receitas, despesas, acordos, cobranças, unidades, condomínios, ocorrências, reservas, tickets, processos judiciais, and relatórios all have substantial lifecycle coverage including create/edit/delete/liquidar/estornar operations. Minor gaps exist (no delete for fornecedores or comunicados, no get-by-id for condominios/cobrancas, no ticket status update), but agents can work around most of them.