superlogica_historicocobranca_create
CRM de Cobrança: Criar agendamento (POST /historicocobranca). [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
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The '[write, altera dados]' tag is consistent with readOnlyHint=false and confirms the operation mutates data, but this mostly duplicates annotation info. The POST endpoint is useful extra context, yet side effects, required permissions, and failure behavior are not disclosed.
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 extremely compact and front-loaded with the action, and the tags are not wasteful. It could be slightly more informative without harming conciseness, but the current wording has no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a create operation with three undocumented string parameters and no output schema, this description is far too thin. It omits the request payload shape, required fields, and typical usage examples, leaving the agent to guess how to invoke the tool correctly.
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?
Input schema has 3 parameters (body, query, account) with 0% schema description coverage, and the description provides no explanation of any parameter. An agent cannot infer what values should go in body, query, or account or whether they are required.
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 names a specific action ('Criar agendamento' - create scheduling) and resource ('historicocobranca'), reinforced by the HTTP verb POST and path. The create verb clearly distinguishes it from sibling list/update tools for the same resource.
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 gives no guidance on when to use this tool versus alternatives such as superlogica_historicocobranca_update or list. The 'create' wording implies usage for new appointments, but no explicit context or exclusions is provided.
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.