Skip to main content
Glama
Sign In
eventin-mcp-server

eventin-mcp-server

by emaratHossain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_booking_stats

Retrieve summary statistics for bookings, including total counts and key metrics, to assess booking performance and trends.

Instructions

Get summary statistics of bookings

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only mentions 'get', which implies a read operation, but does not describe permissions, side effects, limitations, or response characteristics. The output schema helps with return format, but behavioral transparency is sparse.

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 concise sentence: 'Get summary statistics of bookings'. It is front-loaded with the verb and resource, with no filler or redundant information. Every word earns its place.

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?

The tool is simple (zero parameters) and has an output schema, so the description doesn't need to explain return values. However, it lacks usage context, limitations, or any behavioral notes, making it minimally viable but not comprehensive. Given the simplicity, it is acceptable but could be improved with guidance on using it alongside get_bookings.

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 has zero parameters, so the baseline score is 4 per the guidelines. The description adds no parameter semantics because there are no parameters to describe, and the schema coverage is trivially complete.

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 clearly states the verb 'Get' and the resource 'summary statistics of bookings'. It differentiates from the sibling tool get_bookings by indicating aggregated data rather than raw bookings, though it doesn't explicitly compare. It is specific enough to convey the tool's basic function.

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?

No guidance is provided on when to use this tool versus the sibling get_bookings. The description lacks any context about scenarios, prerequisites, or exclusions, leaving the agent without comparative direction.

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