procfy_list_contacts
Read-onlyIdempotent
Lista contatos (clientes/fornecedores) da Procfy. Paginado.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| items | No | ||
| account | No | ||
| filters | No |
Procfy
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?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's main behavioral addition is 'Paginado' (paginated). This is useful but lacks details on pagination behavior (e.g., how to paginate, default page size, or rate limits). The description does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief (one sentence plus one word), which is concise but lacks necessary detail. It is front-loaded with the purpose, but every sentence does not earn its place because critical information (like parameter semantics) is missing.
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?
Given the tool has four undocumented parameters, no output schema, and no usage context, the description is severely inadequate. The agent cannot understand how to use the tool correctly (e.g., what 'filters' accepts, what properties are returned).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It only implies that 'page' and 'items' relate to pagination through the word 'Paginado', but does not explain 'account' or 'filters' at all. No descriptions, formats, or examples are provided for any of the four parameters.
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 clearly states the tool lists contacts (clients/suppliers) of Procfy and is paginated. It uses a specific verb and resource, distinguishing it from siblings like procfy_list_accounts by naming 'contacts'. However, it could be more explicit about what 'contacts' entails (e.g., clients and suppliers) and does not distinguish from other list tools.
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 on when to use this tool versus alternatives like procfy_list_accounts or procfy_list_transactions. There is no mention of prerequisites, context, or exclusions. The agent receives no help in deciding which list tool is appropriate.
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.3/5.0
Disambiguation4/5
Most tools have clear, distinct purposes, especially the procfy_list_* tools which each target a different entity. The platform tools (authenticate, connect, marketplace) are also distinguishable. However, the marketplace tool is multi-purpose with different actions, which could cause some confusion, but descriptions help.
Naming Consistency3/5
Procfy-specific tools follow a consistent 'procfy_verb_noun' pattern, but platform tools (authenticate, connect, marketplace, etc.) lack a prefix and mix verb and noun forms (e.g., marketplace is a noun). This inconsistency in naming conventions across the set reduces clarity.
Tool Count4/5
With 16 tools, it's slightly above the ideal 3-15 range, but still reasonable for a domain covering multiple entities (accounts, bank accounts, categories, etc.). The inclusion of platform tools (6) contributes to the count, but they are necessary for the server's operation.
Completeness2/5
The server provides extensive list operations and a create for transactions, but lacks update/delete for transactions and CRUD for other entities (categories, contacts, etc.). No tool for getting individual entities (except transaction and bank account balance) or creating/modifying them. Significant gaps for a full lifecycle.