Skip to main content
Glama

get_tour

Detail for one holiday/tour by its Sugati/Salesforce tour id. Get the id from a holiday's tour_ids in a search/fetch result.

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": {
      "id": "<id>"
    },
    "name": "get_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSugati/Salesforce tour id (15-18 chars), from a holiday's tour_ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It implies a read-only single-record lookup, but says nothing about the returned payload, behavior on an invalid or unknown id, or whether it errors versus returning empty. For a simple getter the burden is light, but the gaps are real.

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?

Two tight sentences, with the operation stated first and the id-sourcing hint second. Nothing is redundant or padded.

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?

For a one-parameter getter with no output schema, the description covers what the tool fetches and how to obtain the key, but leaves the shape of the returned detail unspecified. An agent knows how to call it but not exactly what it will get back.

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%, and the schema already documents the id as a 15-18 character Sugati/Salesforce tour id sourced from a holiday's tour_ids. The description restates that provenance rather than adding new meaning, so the baseline 3 applies.

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 states a specific verb and resource: retrieve the detail record for a single holiday/tour, keyed by a Sugati/Salesforce tour id. That distinguishes it from the list-oriented siblings (search, fetch, list_products), though it never names an alternative outright.

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?

It gives a concrete prerequisite workflow: obtain the id from a holiday's `tour_ids` in a `search` or `fetch` result before calling this tool. It does not state when not to use it or what to do if the id is unknown, so it stops short of full routing guidance.

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