Skip to main content
Glama
Sign In
Flowteller API MCP Server

Flowteller API MCP Server

Official
by flowteller-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_origins

List available origin locations for creating bookings. Optionally filter by provider such as 'bus', which is the default.

Instructions

Get a list of available origin locations for bookings.

Args:
    provider: The booking provider name (e.g., 'bus', 'mysafari', 'otapp'). Default is 'bus'.

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

Input Schema

NameRequiredDescriptionDefault
providerNobus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not explicitly state read-only status, authentication needs, rate limits, or return format. The 'Get' verb implies a read operation, but this is not stated.

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?

The description is concise and front-loaded with the purpose. The Args block is directly relevant and contains no filler.

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 simple getter with one parameter, the description covers the core function correctly. However, without an output schema, it does not specify the structure of the returned list (e.g., strings vs objects), which would improve completeness.

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 schema lacks descriptions, but the description's Args section explains the provider parameter with examples ('bus', 'mysafari', 'otapp') and its default value. This adds meaningful context beyond the schema's bare property definition.

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 clearly states the tool retrieves a list of available origin locations for bookings, using a specific verb ('Get') and resource. It is implicitly distinguished from sibling get_destinations via the origin/destination contrast, though not explicitly named.

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?

No guidance is provided on when to use this tool versus alternatives like get_destinations or search_trips. There is no mention of prerequisites, exclusions, or context beyond the general 'for bookings' phrase.

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

Deploy Server

Other Tools