superlogica_fornecedores_list
Read-onlyIdempotent
Despesas: Listar favorecidos (GET /fornecedores/index).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description aligns with the annotations: 'Listar' and 'GET' match readOnlyHint=true, idempotentHint=true, and destructiveHint=false. It adds the endpoint and domain context beyond the annotations, but does not disclose details such as authentication needs, pagination, or response behavior. No contradiction with annotations.
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 compact phrase with no filler, and it front-loads the domain category and action. It is appropriately concise for a simple list tool, though it could still carry more useful detail without becoming verbose.
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 two undocumented parameters and no output schema, the description leaves important context missing: what 'query' and 'account' mean, whether they are optional filters, and what the returned list contains. The annotations cover safety but not invocation details.
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?
Schema description coverage is 0% and the description does not mention the 'query' or 'account' parameters at all. The agent receives no additional meaning about what these parameters control or how they should be formatted.
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 specific verb ('Listar') and resource ('favorecidos'), and adds the endpoint 'GET /fornecedores/index' plus the domain context 'Despesas'. It is clear enough to identify the tool's function, though it does not explicitly differentiate it from similar list tools like superlogica_contatofavorecido_list.
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, such as superlogica_contatofavorecido_list or superlogica_despesas_list. The 'Despesas' prefix and endpoint give context, but there are no explicit usage conditions or exclusions.
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.