Skip to main content
Glama
Sign In
Ploomes MCP Server

Ploomes MCP Server

by JoseAlmeida-Ploomes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

buscar_produtos_contato

Search for products associated with contacts in Ploomes CRM. Filter by product name or contact ID to locate specific product-contact records.

Instructions

Buscar produtos associados a contatos no Ploomes CRM.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_produtos_contato"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeNo
paginaNo
contato_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description says 'Buscar' (search) implying read-only, but no annotations confirm this. It does not disclose authentication needs, side effects, or limitations. For a tool with no annotations, the description should provide more behavioral context.

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 a single sentence with no extra words, but it is too brief for a tool with three parameters and no output schema. It is concise but lacks necessary detail, making it borderline average.

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 no output schema, no annotations, and 0% parameter description coverage, the description is severely incomplete. It does not explain return values, pagination behavior, or filter logic, leaving the agent with insufficient information to use the tool effectively.

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 coverage is 0%, and the description adds no explanations for parameters. While parameter names (nome, pagina, contato_id) are somewhat self-explanatory, the description fails to clarify their usage, format, or optionality beyond the schema defaults.

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 searches for products associated with contacts in Ploomes CRM. It distinguishes from siblings like 'buscar_produtos' (general product search) by specifying the association context. However, it could be more detailed about the scope of the search.

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 explicit guidance on when to use this tool versus siblings like 'buscar_produtos' or 'salvar_produto_contato'. The description implies it's for searching associations, but does not provide when/when-not criteria or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools