HebrewCore by baba Hebrew

Translate clinical English to verified Hebrew

clinical_translate

Translate a complete English clinical text (a discharge summary, patient instructions, a visit note, a model's answer) into Israeli medical Hebrew for a clinician or a patient. Drug names, doses, lab values, units, ICD-10 codes, clinical abbreviations, identifiers and every number are kept exactly; every sentence is checked for numbers, negation and laterality and reviewed for meaning. A sentence that fails is retried, then returned in English with status fallback: unverified Hebrew is never returned. Treat fallback sentences as untranslated.

audience: clinician (default, keeps BID/PO shorthand) or patient (plain words). Pass the patient's medication and problem lists as protected_terms, names as redact_terms (hidden from the model), reader_gender and patient_gender when known, and date_order (US records are MDY). Needs a key with Clinical access (the medical scope). Uses the monthly character quota.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bidi`	No	`isolate` wraps English values in Unicode isolates so "5 mg" never renders as "mg 5". `none` returns plain text.	isolate
`text`	Yes	English text, 1 to 20,000 characters. Markdown lists, headings and tables keep their structure. Counts toward the monthly character quota.
`audience`	No	Who reads the Hebrew. `clinician` (default) keeps shorthand such as BID and PO; `patient` writes dosing shorthand (BID, PRN) as plain words.	clinician
`glossary`	No	English term → required Hebrew rendering. Up to 500 entries.
`date_order`	No	How to read ambiguous numeric dates in the source. US records are MDY.	MDY
`date_style`	No	`hebrew` writes "4 במרץ 2026"; `iso` writes 2026-03-04; `keep` leaves unambiguous dates as written (an ambiguous one is still rewritten). A two-digit year is kept as written.	hebrew
`redact_terms`	No	Kept verbatim and never shown to the model (patient and staff names). Up to 200.
`reader_gender`	No	Gender of the reader, the person the text calls "you". Omit when unknown.
`patient_gender`	No	Gender of the patient in third-person references. Inferred from he/she when omitted.
`protected_terms`	No	Kept verbatim. Pass the patient's medication and problem lists from the record. Up to 500, each up to 200 characters. Added to the account terms list for this request.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Request identifier.
`text`	No	The whole Hebrew document: every segment joined with its prefix and suffix.
`stats`	No
`usage`	No
`segments`	No	One entry per sentence, in order.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the exact preservation rules for drug names, doses, lab values, and numbers, as well as the retry-and-fallback behavior with the `fallback` status. It also explains that unverified Hebrew is never returned and warns the agent to treat fallback sentences as untranslated, which is critical operational knowledge.

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 dense but every sentence earns its place, front-loading the core behavior before moving to parameter guidance. It avoids fluff and organizes information into clear, scannable sections.

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?

Covers authentication requirements, quota implications, fallback semantics, audience-specific behavior, and how to handle sensitive terms. With an output schema available, the description does not need to explain return values, and nothing essential for correct invocation is missing.

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, but the description adds meaningful guidance by explaining how to populate protected_terms from the patient's medication and problem lists, why redact_terms should contain names, and when to pass reader_gender, patient_gender, and date_order. This contextual advice helps an agent make better parameter choices than the schema alone would.

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 ('Translate'), a precise resource ('complete English clinical text') and the target output ('Israeli medical Hebrew'), with concrete examples of accepted inputs. It clearly differentiates itself from the generic sibling 'translate' by emphasizing clinical verification and the fallback behavior.

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?

Provides clear context about when to use the tool and how to configure it for the audience, protected_terms, redact_terms, and date_order. It does not explicitly name alternative tools or state when not to use it, but the clinical-specific framing makes the intended use obvious.

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

All HebrewCore by baba Hebrew 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.