Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Embudo de ventas

sales_funnel
Read-only

Track carts opened, payments started, and payments completed per course, plus abandonment metrics. Identify drop-off points in the sales funnel using read-only classroom data.

Instructions

[Administrador del aula · solo lectura] Cuántos carritos se abrieron, cuántos pagos se iniciaron y cuántos se pagaron, más lo abandonado por curso. Sin datos de contacto.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "classroom_id": "<classroom_id>"
    },
    "name": "sales_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint and openWorldHint, so the safety profile is covered. The description adds two pieces of non-schema behavior: the caller effectively needs classroom-administrator rights, and the output deliberately excludes contact data (a privacy constraint on the result). It does not mention pagination, time windows, or freshness, which keeps it out of the top band.

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?

Two terse sentences: the scope/role tag first, then the metric list, then the privacy caveat. No filler. The dense enumeration of funnel stages is slightly compressed but still readable and front-loaded.

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?

For a one-parameter, read-only analytics tool with no output schema, the description does the necessary work by enumerating what is measured and what is excluded. Missing are a time-range assumption (does it cover all time or a default window?) — the only real gap an agent would want closed before calling.

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?

There is a single parameter with 100% schema description coverage ("Aula", uuid format with a strict pattern), so the schema carries the burden and the baseline is 3. The phrase "por curso" adds a hint that results are broken down by course within the given classroom, but nothing further about how the id is obtained or resolved.

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 names the exact metrics returned — cars opened, payments initiated, payments completed and abandonment — and scopes them per course within a classroom. That is a concrete verb/resource picture an agent can act on. It stops short of naming sibling sales_summary, so the distinction between funnel counts and a summary is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The bracketed "Administrador del aula · solo lectura" tag implies the caller must be acting on a classroom they administer and that the call is non-mutating, which is useful context. However, there is no explicit when-to-use statement and no routing to sales_summary or list_sales, so the agent must infer that this is the per-classroom funnel view rather than the broader sales view.

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