Skip to main content
Glama
Sign In
CE3X-MCP-Server

CE3X-MCP-Server

by jmcaamanog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Analizar Plano Arquitectura Pdf

analizar_plano_arquitectura_pdf
Read-onlyIdempotent

Parse vector architectural PDF plans to extract room areas (m²) and window/door schedules for CE3X energy efficiency projects.

Instructions

Abre y analiza un plano arquitectónico en PDF vectorial mediante PyMuPDF, extrayendo superficies útiles de estancias (m²) y cuadros de carpintería de huecos y ventanas.

Cuándo usar: Utilice esta herramienta cuando disponga de planos de planta en PDF para extraer estancias, cotas y cuadros de ventanas. Para modelos tridimensionales IFC use 'analizar_modelo_bim_ifc'.

Comportamiento y efectos secundarios: Operación de lectura y parseo vectorial (Read-Only). No altera el archivo PDF de entrada. Emite progreso interactivo a FastMCP.

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": {
      "pdf_path": "<pdf_path>"
    },
    "name": "analizar_plano_arquitectura_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_pathYesRuta absoluta o relativa al archivo PDF que contiene el plano arquitectónico de distribución.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pdf_path / description
      Added value: +"Ruta absoluta o relativa al archivo PDF que contiene el plano arquitectónico de distribución."
  2. First observedv1.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds real context: vector parsing via PyMuPDF, explicit statement that the input PDF is not modified, and that interactive progress is emitted to FastMCP. It stops short of covering error/failure behavior for malformed or raster PDFs.

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?

Front-loaded with purpose, then labeled sections for usage and side effects, so an agent can skim. Slightly verbose with the header scaffolding, but every sentence carries information.

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?

With an output schema present, return values need not be explained, and the description covers purpose, alternatives, input expectations, and side effects. Nothing an agent needs to call this correctly is missing.

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?

Only one parameter (pdf_path) at 100% schema description coverage, so the schema already documents it. The description adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 (abre y analiza) and resource (plano arquitectónico en PDF vectorial), names the engine (PyMuPDF) and the concrete outputs (superficies útiles en m² y cuadros de carpintería). It clearly differentiates itself from the IFC sibling tool.

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

Usage Guidelines5/5

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

The 'Cuándo usar' block gives an explicit condition (planos de planta en PDF) and routes the agent to the alternative ('analizar_modelo_bim_ifc') for 3D IFC models. No inference required.

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