Skip to main content
Glama
io.github.mohammad-abbasi-sh/flixtrain-mcp

io.github.mohammad-abbasi-sh/flixtrain-mcp

flixtrain_health

Checks whether the FlixBus search API is reachable now and returns ok, blocked, or error status with HTTP code and probed URL.

Instructions

Check whether the FlixBus search API is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the three outcome states, the HTTP codes behind each, what 'blocked' means (bot wall or rate limit), and the cost profile (one polite request, no listing fetches). It does not mention auth or retry/backoff expectations, which is the remaining gap.

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?

Three short sentences, front-loaded with the purpose, then the return values, then the cost/side-effect disclaimer. Every sentence adds information and none is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter health probe with an output schema already documenting the response shape, this covers everything an agent needs: what it checks, what the outcomes mean, and that it is cheap and non-destructive.

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 4 applies; no parameter information is needed or missing.

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: probe whether the FlixBus search API is reachable. That is clearly distinct from the sibling search tools. The only wrinkle is the name says flixtrain while the description targets the FlixBus search API, a small naming mismatch that leaves a hint of ambiguity about scope.

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?

Implies a diagnostic use case ("reachable right now") and draws a boundary by saying it does not fetch any listings, which routes data needs to the search siblings. It stops short of explicitly saying when to prefer this over the search tools or what to do on a 'blocked' result.

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