Skip to main content
Glama
novacrm-mcp

novacrm-mcp

novacrm_get_store_visits

Retrieve anonymous aggregated public store visit metrics for the last 30 days, including unique visitors, showcase views, checkout rate, devices, and traffic sources.

Instructions

Acessos à loja pública nos últimos 30 dias (dados anônimos agregados): visitantes únicos, visualizações da vitrine, produtos mais vistos, sacolas abertas, taxa de checkout, série diária, dispositivos e origem do tráfego.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two meaningful traits: the data is anonymous and aggregated, and the window is fixed at 30 days with no parameters. It does not state read-only safety explicitly, nor return format, freshness, or rate limits, leaving real gaps for a tool with zero structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the resource and time window, followed by a compact enumeration of returned metrics. Every listed item earns its place because there is no output schema to carry that information.

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

Completeness4/5

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

With no input parameters, no annotations, and no output schema, the description's enumeration of returned metrics is exactly the compensation needed. It is nearly complete; only the absence of any note on data freshness or how the aggregate is scoped (store-level vs. account-level) leaves a small gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the fixed 30-day window in the description usefully confirms the agent cannot narrow the range.

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+resource ("Acessos à loja pública") plus a fixed window ("últimos 30 dias") and enumerates the metrics returned, so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from sibling analytics tools like novacrm_get_metrics or novacrm_get_store, which keeps it below 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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as novacrm_get_metrics, which is the closest sibling for analytics. The only implicit cue is the fixed 30-day scope, which tells the agent this is not parameterizable but not when to prefer it.

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