Skip to main content
Glama

Service information

get_service_info
Read-only

Full business facts for GC Airport Transfers — private (not shared-shuttle) fixed-price airport and cruise transfers in Queensland (Gold Coast, Brisbane, Byron Bay / Northern NSW): fleet, pricing list, policies, service area and contact details. Use this before answering questions about the service.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the content scope of what comes back, which is genuinely useful, but says nothing about size, freshness or the shape of the response beyond topic categories.

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?

A single front-loaded sentence names the subject first and then the contents, with no filler. It is dense with parentheticals (private vs shared-shuttle, the region list) but each one carries real disambiguating value rather than padding.

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 and no parameters, the description must carry the burden of telling the agent what it will get back, and it does so by listing the categories of business facts. It is nearly complete; only the depth or format of those facts is left unspecified.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals a parameterless lookup by not implying any input is required.

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 names a specific resource (GC Airport Transfers business facts) and enumerates its scope: fleet, pricing list, policies, service area, contact details. It also pins down the offering as private fixed-price airport/cruise transfers in a named region, so an agent can distinguish this informational tool from the transactional siblings check_availability, get_quote and request_booking.

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?

"Use this before answering questions about the service" gives a clear trigger condition and even orders it ahead of other calls. It stops short of explicitly naming the siblings or stating when-not to use it (e.g. for live pricing use get_quote), so routing is implied rather than spelled out.

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.