Skip to main content
Glama

Bhutan Trips by Druk Asia

List Druk Asia v1 API endpoints

list_endpoints
Read-only

Returns a concise reference of all Druk Asia v1 API endpoints and the MCP tool that wraps each one.

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": "list_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the output is a 'concise reference' mapping endpoints to the MCP wrappers, which tells the agent something about content, but it gives no detail on format (table vs. JSON), whether the list is exhaustive or versioned to v1 only, or how large the payload is.

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?

A single front-loaded sentence with no filler — the resource ('all Druk Asia v1 API endpoints') is stated before the qualifier about MCP wrapping. Nothing is redundant with the title.

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?

There is no output schema, so the description carries the burden of describing the return shape, and 'concise reference' is vague — it doesn't say whether items include HTTP paths, methods, or descriptions alongside the tool names. For a zero-parameter, read-only catalog tool this is close to sufficient, but the missing return-shape detail is a real 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 of 4 applies. The empty object schema is consistent with the description's claim that it returns the full reference unconditionally.

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?

States a concrete verb and resource: returns a reference of all Druk Asia v1 API endpoints plus the MCP tool wrapping each. An agent can immediately tell this is a meta/discovery tool rather than one of the domain tools (list_destinations, get_booking, etc.). It stops short of explicitly contrasting itself with those siblings, so it lands at 4 rather than 5.

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: because the description says it enumerates every endpoint and its wrapping MCP tool, an agent can infer it is for discovery/routing. There is no explicit 'call this when you don't know which tool to use' statement, no exclusions, and no mention of alternatives such as the individual list_* tools.

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