Academic Writer MCP

Recharger les profils

reload_domain_profiles

Idempotent

Reload profile files after adding or editing a custom domain profile so the Academic Writer MCP uses the updated settings immediately.

Instructions

Relit les fichiers de profils (après ajout ou modification d'un profil personnalisé).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`count`	Yes
`domains`	Yes
`load_errors`	Yes	Profils écartés car invalides.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety and repeatability are covered. The description adds the useful context that this is a refresh triggered by profile changes, but it does not explain what state gets reloaded, whether in-memory changes are discarded, or whether the operation can fail on malformed profile files.

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?

One sentence, front-loaded with the action and followed by the condition that motivates it. Nothing is wasted and nothing is buried.

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?

With no parameters and an output schema available, the description only needs to convey purpose and trigger, which it does. The remaining gap is minor: it does not say whether the reload takes effect immediately for subsequent calls in the same session.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the schema is trivially complete. The baseline for a parameterless tool applies.

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 ("Relit" / re-reads) and resource ("les fichiers de profils"), so the agent knows this refreshes profile definitions rather than listing or fetching a single profile. It does not explicitly contrast itself with siblings like list_domain_profiles or get_domain_profile, but the action is unambiguous.

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?

The parenthetical "après ajout ou modification d'un profil personnalisé" gives an explicit trigger condition: call this after adding or editing a custom profile. There is no statement of when NOT to use it and no named alternative, keeping it short of a 5.

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

Deploy Server