Fitralo

Search carriers

search_carriers

Read-onlyIdempotent

Find road freight carriers in Europe that run a route and offer the equipment, services or certificates a load needs. Write the query plainly: the places of loading and delivery (town, postcode or country), then what is needed, e.g. "reefer from Venlo to Rome", "ADR tank Rotterdam to Poland", "groupage Germany to Italy, tail lift". "based in Italy" keeps carriers based there. Returns the carriers that fit, best first, with what the search understood: if that is not what the user meant, phrase the query again. It returns at most limit carriers (10 unless set, up to 25); carriers_that_fit counts all that fit, and results_url shows them all on fitralo.com. When nothing fits exactly, carriers_that_fit is 0 and the list has the carriers that come closest. A query without a route or need returns an error that says how to write it. Then call get_carrier for contact details. Read-only and without an account: it changes and books nothing. At most 300 calls an hour from one address, for all tools together.

Input Schema

Name	Required	Description	Default
`limit`	No	How many carriers to return.
`query`	Yes	The route and needs in plain words, in English or the language given.
`language`	No	The user's language as a two-letter code, when Fitralo has it: labels such as services and equipment, the profile description where it is translated, and the links to the site follow it.	en
`specialists_only`	No	Only carriers for whom this route (or area) is their own line, not one among many.

Output Schema

Name	Required	Description
`carriers`	Yes
`results_url`	Yes	All results on fitralo.com, with filters for the user.
`specialists`	Yes	Of those that fit, how many have this route as their own line; null without a place in the query.
`understood_as`	Yes	The route and needs the search read in the query.
`carriers_that_fit`	Yes	All carriers that fit; when 0, the list has those that come closest.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedOutput schema / properties / carriers / items / properties / takes_requests

Added value: +{
+  "description": "send_request can ask this carrier for a price; without it, the carrier gets no transport request through Fitralo.",
+  "type": "boolean"
+}

changedOutput schema / properties / carriers / items / required

Previous value: -[
-  "name",
-  "profile_url",
-  "location",
-  "fits_exactly",
-  "specialist_on_route",
-  "verified_by_company",
-  "last_checked",
-  "services",
-  "equipment",
-  "certificates"
-]New value: +[
+  "name",
+  "profile_url",
+  "location",
+  "fits_exactly",
+  "specialist_on_route",
+  "verified_by_company",
+  "last_checked",
+  "services",
+  "equipment",
+  "certificates",
+  "takes_requests"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / language / description

Previous value: -"Language of the labels and of the links to the site: the user's language, when Fitralo has it."New value: +"The user's language as a two-letter code, when Fitralo has it: labels such as services and equipment, the profile description where it is translated, and the links to the site follow it."

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real context beyond them: no account needed, nothing is booked or changed, a 300-calls-per-hour-per-address limit shared across all tools, best-first ordering, and the closest-match fallback when carriers_that_fit is 0.

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?

Purpose and the query-writing instruction are front-loaded and every example earns its place, but the closing sentences about carriers_that_fit and results_url re-explain return values that the output schema already documents. Slightly long, though dense rather than padded.

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?

Complete for a search tool: input guidance, error behavior, rate limits, and next-step routing are all present, and an output schema exists so return values need no explanation. The only gaps are the unaddressed specialists_only and language parameters.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by teaching the syntax of the free-text query, which is the only ambiguous parameter, and restating the limit cap ('10 unless set, up to 25'). It says nothing about specialists_only or language, leaving those to the schema.

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?

States a specific verb and resource ('Find road freight carriers in Europe') plus the discriminating scope: route, equipment, services, certificates. It also names the downstream sibling ('Then call get_carrier for contact details'), so an agent can place it in the workflow without opening another 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?

Gives concrete query patterns ('reefer from Venlo to Rome', 'ADR tank Rotterdam to Poland', 'groupage Germany to Italy, tail lift'), explains the 'based in Italy' qualifier, tells the agent to rephrase when the parsed query is wrong, and routes contact-detail lookups to get_carrier. Failure modes (query without route or need) are also spelled out.

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

All Fitralo tools Inspect

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

Need Help?