Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_list_coupons

Lists a NovaCRM store's discount coupons so AI assistants can review available codes, campaign details and redemption rules via the v1 API.

Instructions

Lista os cupons de desconto da loja.

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_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It never states that the call is read-only, whether results are paginated or capped, whether expired/inactive coupons are included, or what fields come back — all meaningful for an agent deciding how to use the output.

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 short sentence with no filler, and the verb-plus-resource core is front-loaded. It is efficient rather than padded, though the brevity is a symptom of under-specification rather than deliberate economy.

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 zero-parameter list tool there is little an agent strictly needs in order to call it, and no output schema exists to explain the return. Still, the description omits whether the result set is filtered (active only), how large it may be, or whether pagination exists — gaps that matter when a coupon list could be long.

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

Parameters4/5

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

The schema has zero properties, so there are no parameters to document and the baseline of 4 applies. The description correctly implies the tool takes no arguments, consistent with the empty object 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?

States a specific verb ("Lista") and a specific resource ("os cupons de desconto da loja"), so an agent immediately knows this is a read operation over coupons. It does not, however, distinguish itself from sibling coupon tools such as novacrm_create_coupon or novacrm_validate_coupon, so it falls short of a 5.

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 call this versus the other coupon-related siblings, no prerequisites, and no mention of scope (all coupons vs. active only). The only usage signal is the implicit "list" semantics.

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