Skip to main content
Glama

Lingoris — traduction assermentée

Estimer le prix d'une traduction assermentée

get_price_estimate
Read-only

Prix ferme TTC d'une traduction assermentée Lingoris pour une paire de langues, un nombre de pages et un délai. Une page tarifaire = 250 mots : le nombre de pages définitif est déterminé à l'upload du document sur lingoris.fr, ce prix vaut donc pour le nombre de pages indiqué. TVA française 20 % incluse. Aucun tarif dégressif : le prix dépend uniquement de la langue, du nombre de pages et du délai.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "get_price_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoNombre de pages tarifaires (250 mots par page).
sourceNoLangue du document d'origine (défaut : "fr").fr
targetYesLangue de destination — nom français, anglais ou code ISO ("anglais", "en", "arabe").
urgencyNostandard = 24 h ouvrées, priority = 12 h, urgent = 6 h (uniquement si l'anglais est la langue source ou cible).standard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / urgency / description
      Previous value: -"standard = 24 h ouvrées, priority = 12 h, urgent = 6 h."New value: +"standard = 24 h ouvrées, priority = 12 h, urgent = 6 h (uniquement si l'anglais est la langue source ou cible)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: 20% French VAT is included, there are no volume discounts, and the quoted price is firm only for the page count supplied. It stops short of saying what the response contains or in which currency the figure is expressed (EUR is only implied by the VAT mention).

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?

Four sentences, front-loaded with the definition of what the price covers, followed by the pricing rules. Each sentence carries information. Minor redundancy between 'le prix dépend uniquement de la langue, du nombre de pages et du délai' and 'aucun tarif dégressif', which restate the same non-degressive constraint twice.

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?

For a read-only, four-parameter pricing tool this is nearly complete: VAT treatment, page definition, firmness caveat, and the absence of discount tiers are all stated. With no output schema, the one remaining gap is what the tool returns (an amount, a currency, a breakdown) — the description never says, and EUR is only inferable from the VAT reference.

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 schema already documents pages, source, target and urgency including the 250-words-per-page rule and the English-only constraint on urgent. The description reinforces the semantics by stating price depends only on language, pages and delay and by ruling out degressive tiers, which resolves a pricing question the schema cannot express.

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?

The description names a specific resource (prix ferme TTC d'une traduction assermentée Lingoris) and the exact dimensions that determine it: language pair, page count, and turnaround. It is clearly distinct from get_order_status and list_languages by domain, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers 'call this when a customer wants a certified-translation price'. There is no explicit when-to-use/when-not statement and no routing against the two sibling tools. The caveat about page count being finalized at upload is contextual, not a usage rule.

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.

Resources