Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_list_proposals

List commercial proposals with status filtering and pagination to retrieve proposal records from a NovaCRM store; use limit, offset, and status to narrow results.

Instructions

Lista propostas comerciais com filtro por status e paginação.

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": "novacrm_list_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItens por página (1–100, padrão 50)
offsetNoDeslocamento da paginação (padrão 0)
statusNoFiltrar por status (padrão: todas)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. The verb 'Lista' implies a read-only, non-destructive operation, and the mention of filtering and pagination adds useful behavioral context, but the description says nothing about what fields are returned, result ordering, or whether pagination has a total count.

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?

A single efficient sentence with no waste, front-loading the resource (proposals) and then its two scoping controls. Slightly under-specified rather than over-long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read-only list tool with full schema coverage and no output schema, the description covers the essentials but omits what a caller gets back and how results are ordered, which would matter for an agent deciding between this and get_proposal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including an enum for status and explicit defaults for limit (50) and offset (0), so the schema does the heavy lifting. The description only echoes that status filtering and pagination exist, adding no syntax or format detail beyond the schema.

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 and resource ('Lista propostas comerciais') and mentions the two dimensions that shape the result (status filter and pagination). It is clearly a list operation, but it never distinguishes itself from siblings like novacrm_get_proposal or novacrm_list_opportunities, leaving the agent to infer the boundary.

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?

There is no guidance on when to use this versus novacrm_get_proposal for a single record, nor any mention of prerequisites or exclusions. The agent must infer usage from the verb alone.

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