Skip to main content
Glama
Sign In

TripWorks Tour and Activity Booking

by com.tripworks
OverviewDiscussionsAdmin

Run a read-only operation

query
Read-only

Run a read operation (kind read in discover) such as a list, a get, a search, a manifest or analytics. Rejects write operations; use execute for those. Always pass tool (the operation name) and put the operation's own arguments inside arguments, as listed by discover.

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

Input Schema

NameRequiredDescriptionDefault
toolNoRequired: the read operation name, from discover.
argumentsNoArguments for the operation, as listed by discover. Omit when it takes none.

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 and openWorldHint=false, so the safety profile is structured. The description adds the rejection-of-writes rule and the two-level invocation pattern, but says nothing about what happens on an unknown operation name or what the response looks like, since returns vary per dispatched operation.

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?

Three short sentences, front-loaded with scope before the sibling routing, and every clause carries routing or invocation information. Minor redundancy: 'Always pass tool' restates the schema's Required marker and the operation-name source already stated in the first sentence.

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 two-parameter dispatcher with no output schema, the definition covers the read-only contract, the discover-to-execute workflow, and the nested-argument convention. It is only slightly incomplete on error behavior for invalid operation names and on the fact that return shapes are operation-dependent.

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 both parameters carry descriptions, so the schema already documents 'tool' and 'arguments'. The description reinforces that arguments must match the operation as listed by discover, but adds no syntax or format detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 the verb and resource ('run a read operation'), enumerates concrete operation families (list, get, search, manifest, analytics), and explicitly contrasts itself with a named sibling ('use execute for those'). An agent can distinguish query, discover, and execute without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use this tool (read operations), when not to (write operations are rejected), and which alternative handles the excluded case (execute). It also routes operation discovery to 'discover', so the routing decision is fully specified.

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

All TripWorks Tour and Activity Booking toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources