apibase

Search Tatoeba Sentences

language.tatoeba.search

Read-onlyIdempotent

Search 13M parallel sentences across 429 languages (CC-BY 2.0 FR). Filter by source language, optional translation language, audio availability, and free-text keyword. Sort by relevance/random/created/modified. Tatoeba

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort order — "relevance" (default), "words" (length), "created", "modified", or "random".
`limit`	No	Max sentences to return (default 10, max 50).
`query`	No	Optional keyword search inside sentence text.
`language`	No	ISO 639-3 language code of the source sentence (default "eng"). Use tatoeba.languages to discover codes.
`has_audio`	No	Filter to sentences that have a human audio recording attached.
`translation_lang`	No	ISO 639-3 code of a target language — only return sentences that have a translation into this language.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds license (CC-BY 2.0 FR) but no behavioral details like pagination, response structure, or rate limits.

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?

Two concise sentences, front-loaded with scale and purpose, no redundant information.

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?

Given annotations, the description covers key aspects: filters, sort, and reference to language codes. Does not mention optional nature of all parameters or output schema, but these are likely covered elsewhere.

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?

100% schema description coverage means parameters already well-documented. Description summarizes filter options and references tatoeba.languages, but adds no new semantic meaning.

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?

Description clearly identifies tool as search for parallel sentences across languages, mentions scale (13M sentences, 429 languages), and distinguishes from sibling tools like tatoeba.languages and tatoeba.sentence.

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?

Mentions tatoeba.languages for discovering language codes, provides filter and sort options, but does not explicitly state when to use this vs alternatives like translation query.

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

All apibase 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.