Skip to main content
Glama
chrischall

evite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

evite_list_events

Read-only

List Evite events you host or attend, filter by status, title, or role (host/guest), and page through results with a totals breakdown.

Instructions

List your Evite events (GET /services/events/v1/). Returns events plus a totals breakdown. filterBy=others returns events where you are a guest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Evite's payload untouched. No field projection: this server has no verified record of which Evite fields matter, and inventing one would risk dropping a field a caller needs.
filterNoFree-text search over event titles.
offsetNoPagination offset.
statusNoRepeatable status filter (upcoming, draft, archived, past, canceled).
filterByNoWhose events to list: all, host (you are hosting), or others (you are a guest).all
numResultsNoPage size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Evite's payload untouched. No field projection: this server has no verified record of which Evite fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value a schema cannot: it discloses the return shape ('events plus a totals breakdown') despite no output schema, and clarifies the guest view for filterBy=others. It omits pagination behavior, sort order, and any rate or auth constraints.

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?

Three tight sentences with the core purpose and return shape front-loaded and no filler. The endpoint path '(GET /services/events/v1/)' is arguably noise for an agent, but it does reinforce the read-only nature of the call.

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 six fully documented parameters, read-only/open-world annotations, and no output schema, the description covers the essentials: what it lists, what comes back, and the one non-obvious filter mode. Remaining gaps (ordering, pagination semantics beyond the schema, cross-tool sequencing) are minor for a zero-required-parameter listing 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 description coverage is 100%, so every parameter is already documented in detail, which sets the baseline at 3. The description's only parameter content ('filterBy=others returns events where you are a guest') largely restates the schema's own 'others (you are a guest)' text, adding no new syntax, defaults, or interaction rules.

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 and resource ('List your Evite events') and even pins the underlying endpoint, so the agent knows this retrieves a collection rather than a single record. The resource name implicitly separates it from siblings like evite_list_guests, evite_list_templates, and evite_get_event, though no sibling is named explicitly.

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?

Usage is implied rather than stated: the agent can infer this is the browsing entry point for events, and the filterBy=others note hints at a guest-perspective mode. There is no explicit when-to-use/when-not guidance, no mention of alternatives (e.g., evite_get_event for a single event), and no prerequisites such as authentication context.

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