Skip to main content
Glama
Sign In
Academic Writer MCP

Academic Writer MCP

by academic-writer-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Extraire les images

extract_document_images
Read-onlyIdempotent

Extracts document images and lists their page, dimensions, and fingerprint, saving copies to the project folder; enable OCR to capture text within images.

Instructions

Liste les images d'un document (page, dimensions, empreinte) ; copies enregistrées dans le dossier du projet.

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": {
      "document_id": "<document_id>"
    },
    "name": "extract_document_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocrNoLire aussi le texte contenu dans les images (OCR, plus lent).
document_idYesIdentifiant du document (voir list_documents).

Output Schema

NameRequiredDescriptionDefault
countYes
imagesYes
warningsNo
images_dirYesDossier des images extraites (relatif au dossier de données).
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, but the description states that copies are 'enregistrées dans le dossier du projet' — a filesystem write side effect. This directly contradicts the read-only annotation and leaves the agent with a misleading safety profile.

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 a single compact sentence with the purpose front-loaded before the side-effect note. It is slightly telegraphic but contains no wasted wording.

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?

An output schema exists, so the description need not explain return values in detail; it appropriately mentions page, dimensions, and fingerprint as output context. However, it omits usage guidance and its saved-copies side effect conflicts with the read-only annotation, leaving a significant behavioral 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 description coverage is 100%, so both parameters (document_id and ocr) are already documented in the schema. The description adds no parameter semantics beyond what the schema provides, making the baseline 3 appropriate.

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 uses a specific verb ('Liste') and resource ('les images d'un document') and adds returned attributes (page, dimensions, empreinte). It is clearly about images, but it does not explicitly contrast itself with sibling extraction tools such as extract_document_content or extract_document_tables.

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 implied by the tool name and the phrase 'images d'un document', so an agent can infer when to call it. However, there is no explicit when-to-use guidance, no prerequisites, and no alternatives named for extracting other document elements.

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

Deploy Server

Other Tools