Academic Writer MCP

Rechercher un terme

lookup_terminology

Read-onlyIdempotent

Find specialized term equivalents in French, Russian, and English, with definitions and usage notes on formulations to avoid when writing academic or technical documents.

Instructions

Trouve un terme spécialisé : équivalents fr/ru/en, définition et formulations à éviter.

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": {
      "query": "<query>"
    },
    "name": "lookup_terminology"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes	Terme en français, russe ou anglais.
`domain_id`	No	Limiter à un profil (facultatif).

Output Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`entries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety and determinism profile is covered. The description adds the content shape (equivalents, definition, avoid-list), which is mildly useful, but says nothing about matching behavior (exact vs. fuzzy), result ordering, or what happens when a term is not found.

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?

A single front-loaded sentence with no filler; every clause (term, three equivalents, definition, formulations to avoid) carries information an agent can act on.

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 is simple, has an output schema that covers return values, and annotations that cover safety, so the description need not say much. Still, it leaves the agent guessing about search matching semantics and empty-result behavior, which for a lookup tool is a real gap.

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 coverage is 67%: query and domain_id are documented inline, while limit is not. The description's mention of fr/ru/en overlaps with what the query field already says, and it adds no meaning for limit or domain_id, so it does not compensate for the coverage gap.

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 verb and resource ("Trouve un terme spécialisé") and enumerates what comes back: fr/ru/en equivalents, a definition, and formulations to avoid. That is enough for an agent to know what the tool does, but it never contrasts itself with any related tool, so it does not reach 5.

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?

There is no statement of when to call this versus anything else, and no prerequisites or exclusions. The use case (looking up a specialized term or its equivalents) is only inferable from the listed return fields, which is weak guidance.

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

Deploy Server