Skip to main content
Glama

Tatoeba Search

tatoeba_search
Read-onlyIdempotent

Search sentences. Use ISO 639-3 codes ("eng","fra","spa","jpn","cmn",...) for from/to.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "hello"
    },
    "name": "tatoeba_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget translation language (default any).
fromNoSource language (default any).
pageNo1-based (default 1).
limitNo1-100 (default 25).
queryYes

Output Schema

NameRequiredDescriptionDefault
pagingNoPagination metadata from API
resultsNoSearch result sentences, limited to requested count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, open-world search. The description adds useful behavioral context by requiring ISO 639-3 language codes for from/to, but it does not explain translation-result behavior, pagination semantics, or what the search actually matches.

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?

The description is two short sentences with no wasted wording, and the language-code guidance is front-loaded after the core action. It is appropriately sized, though it could be slightly more informative about the query parameter.

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?

The tool has rich annotations, an output schema, and mostly documented parameters, so the description does not need to explain return values. However, for a search tool with five parameters, it is still thin on query semantics and when to use language filters, leaving clear contextual gaps.

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?

Schema description coverage is high, and the schema itself documents to/from/page/limit while examples illustrate query usage. The description adds meaningful ISO 639-3 format guidance beyond the schema, but it says nothing about the required query parameter or how query interacts with from/to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource, 'Search sentences', but does not clarify that this is Tatoeba sentence/translation search or what the query searches against. It distinguishes itself somewhat by mentioning from/to language filtering, but the overall purpose remains vague beyond a generic sentence search.

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?

The only concrete guidance is to use ISO 639-3 codes for from/to. It does not explain when to use this tool versus alternatives, when to omit language filters, or any exclusions or constraints on usage.

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.