Skip to main content
Glama
Sign In
A2Me MCP Server

A2Me MCP Server

by Kinnectd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get trip overview

get_trip_overview
Read-onlyIdempotent

Retrieve a complete family trip overview covering dates, destination, attendee RSVPs and pending invites, each person's flights and lodging, and the itinerary of linked events.

Instructions

Everything about a family trip in one view: dates, destination, who's coming (with RSVP and pending invites), each person's travel details (flights and lodging — e.g. 'when does Marcia land'), and the itinerary of linked events.

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

Input Schema

NameRequiredDescriptionDefault
tripNameNoTrip name (fuzzy). Omit to use the only upcoming trip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful context about the response contents (RSVP status, pending invites, flight/lodging details, linked event itinerary) and provides a concrete example ('when does Marcia land'). No contradiction with annotations.

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 with a clear opening summary followed by a colon and a list of included data types. Every element adds value and there is no redundancy or filler.

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

Completeness5/5

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

Despite lacking an output schema, the description thoroughly conveys what the returned data will include, even offering an example question ('when does Marcia land') to clarify the type of detail available. This is sufficient for an agent to set expectations for a composite overview response.

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% with tripName described as 'fuzzy' and optional, with fallback to the only upcoming trip. The tool description itself does not elaborate on parameters, but the schema's description is sufficient, so the baseline 3 is appropriate.

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 tool provides 'Everything about a family trip in one view' and enumerates specific contents (dates, destination, attendees, travel details, itinerary), distinguishing it from sibling getters that focus on individual family members or events.

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

Usage Guidelines4/5

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

The phrase 'in one view' implies using this tool when a holistic overview is needed rather than calling multiple specific getters. However, no explicit alternatives or when-not-to-use guidance is provided, so it falls short of a 5.

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