Skip to main content
Glama

GoTravelX Flight Status

Get connected account

get_account_profile
Read-only

Identify the connected GoTravelX account. Does not spend a result set.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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=false, so safety and locality are covered without the description. The description does add one behavioral fact beyond annotations, namely that the call does not consume a result set, which matters for quota-sensitive agents. However, that phrase is undefined terminology, so the added value is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At two short sentences the definition is well front-loaded, with the identifying verb first. But the second sentence is ambiguous jargon ('result set') whose meaning an agent cannot resolve, so brevity comes at the cost of clarity rather than earning its place.

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?

This is a zero-parameter, read-only identity lookup and an output schema exists, so return values need no explanation. The definition covers what the tool returns conceptually (the connected account) and one cost-related behavior. It is essentially complete for this complexity, with only the ambiguous quota phrasing detracting.

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 and the baseline of 4 applies. Omitting parameter discussion is correct here rather than a gap.

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 specific verb and resource: 'Identify the connected GoTravelX account.' That clearly separates it from get_account_balance and get_flight_status, which target different resources. The second sentence ('Does not spend a result set') is opaque and does not sharpen the purpose statement.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for cases such as needing balance or flight data. The only usage-adjacent signal is the cryptic note about not spending a result set, which implies a cost model but never states when an agent should prefer this call.

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