jotae-mcp

get_event_stats

Get event metrics: registrations, attendance, pitch, CTA clicks, and conversion rate.

Instructions

Retorna métricas do evento: inscrições, presença, pitch, cliques no CTA e taxa de conversão.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_stats"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	ID do evento

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 27, 2026

TDQS

B3.3/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. It only states that metrics are returned but does not disclose whether the operation is read-only, requires special permissions, or has performance implications. Critical behavioral context is missing.

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?

The description is a single sentence that efficiently conveys the tool's purpose and output. It is front-loaded and contains no unnecessary words.

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?

Given the schema coverage is complete and no output schema exists, the description lists the metrics returned. However, it lacks details about time range, data freshness, or potential pagination, which would be helpful for a stats tool.

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 coverage is 100% for the single parameter event_id, but the description does not add semantic value beyond what the schema already provides. It lists the metrics returned but does not explain the parameter format or provide examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retorna' (returns) and the resource 'métricas do evento' (event metrics), listing specific metrics (registrations, attendance, etc.). This distinguishes it from sibling tools like get_event (event details) and list_events (event list).

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 provides no guidance on when to use this tool versus alternatives. It does not mention contexts where metrics are needed or exclude cases where get_event or list_events would be more appropriate.

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