Skip to main content
Glama

Search resort facts

search_facts
Read-onlyIdempotent

Searches the approved, current facts about Magenta Private Island, a luxury all-inclusive private island resort off Placencia, Belize: villas and suites, rates, inclusions, dining and drinks, activities, getting there, families, deposits and cancellation. Returns matching facts in guest-ready wording with their date.

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": {
      "query": "<query>"
    },
    "name": "search_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat the guest asked about, e.g. "deposit", "children", "spa", "transfer", "holiday rates".
topicNoOptional topic filter; see list_topics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent, non-open-world read, so the safety burden is covered. The description adds real context beyond them: the facts are 'approved' and 'current' (a provenance/freshness guarantee) and results come back in 'guest-ready wording with their date,' which tells the agent the output is quotable and time-stamped. It says nothing about result counts, ranking, or pagination behavior.

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 verb and the resort identity; the long colon-separated scope list is load-bearing because it defines what counts as a fact here. Slightly list-heavy, but nothing is wasted or buried.

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?

For a 3-parameter read-only search with no output schema, the description covers purpose, content scope, freshness, and the shape of the return value ('matching facts in guest-ready wording with their date'). The remaining hole is routing: nothing tells the agent why this beats search_site or how_to_book for a given question.

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 67%: query and topic carry descriptions (topic explicitly defers to list_topics), while limit has none and its 1-25 bound is undocumented. The description's category list loosely maps to what query/topic accept but adds no syntax, format, or default guidance beyond the schema, so the baseline of 3 is appropriate.

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?

Specific verb+resource: 'Searches the approved, current facts about Magenta Private Island...' followed by an enumerated scope (villas, rates, inclusions, dining, activities, transfers, families, deposits, cancellation). That is far more than a restatement of the name. It does not, however, explicitly distinguish itself from the sibling search_site or get_policy, so an agent must infer the boundary.

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 only implied: the enumerated fact categories suggest it is for guest-facing factual questions, and the return note ('guest-ready wording') hints at the customer-facing path. There is no explicit when-to-use statement and no named alternative or exclusion versus search_site, get_policy, or how_to_book, all of which plausibly compete for the same query.

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