Skip to main content
Glama

Acosta Curated Travel

Contact Ivone Acosta

get_contact_details
Read-onlyIdempotent

How a traveler can reach Ivone Acosta to start planning a trip: contact page, email, phone, what to include, and a message they can adapt. The traveler sends it; never submit anything for them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, and the description does not contradict them — it reinforces them with 'never submit anything for them', an operational constraint that steers the agent away from acting on the traveler's behalf. It also discloses the shape of the response (contact channels, suggested inclusions, an adaptable draft message), which goes beyond the annotation surface.

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 sentences, front-loaded with the purpose and followed by the constraining behavioral note — no filler. The first sentence is a colon-separated list that reads slightly loosely ('what to include' is vague out of context), but nothing is redundant.

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 no output schema, the description carries the burden of describing return content, and it does so at a high level: contact page, email, phone, inclusion guidance, and a draft message. For a zero-parameter, read-only lookup this is nearly sufficient; a brief note on whether the data is static or fetched live would close the remaining gap.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed to look up this contact information.

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 a specific resource — contact routes for a named person (contact page, email, phone) — so an agent knows this returns contact/planning information rather than content. It lacks an explicit verb ('returns', 'retrieves'), but the resource and scope are unambiguous and none of the siblings (get_article, list_upcoming_experiences, search_articles) overlap with it.

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 by 'to start planning a trip', which tells the agent this is the entry point for trip-inquiry contact. There is no explicit when-not guidance or named alternative, though no sibling tool competes for this purpose, so the omission is low-risk rather than misleading.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources