Skip to main content
Glama

biblioteca_compilar_manifiesto

Read-only

Compile the Markdown legal doctrine library catalog and metrics, then generate distribution bundles for Hugging Face, GitHub, and Google Drive.

Instructions

Compila el catálogo y métricas de la biblioteca online de Markdown de doctrina y genera los paquetes para Hugging Face, GitHub y Google Drive.

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": "biblioteca_compilar_manifiesto"
  }
}

Input Schema

NameRequiredDescriptionDefault
generar_bundlesNoSi es True, empaqueta el tar.gz y prepara la carpeta para Google Drive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that it produces a catalog, metrics and packages for three external platforms, but it does not clarify whether it merely generates local artifacts or actually uploads to Hugging Face/GitHub/Drive — a meaningful ambiguity for an openWorld tool.

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?

One front-loaded sentence with no filler, naming the artifact types and the three target platforms. Slightly dense, but every clause carries information.

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?

With no output schema, the description should say what the tool returns or where the packages land. It never explains the 'manifiesto' the tool is named after, nor the resulting file locations, so an agent knows the intent but not the outcome.

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% and the single parameter generar_bundles is fully documented in the schema. The description never mentions the flag, so it adds no meaning beyond the schema; baseline 3 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?

States a concrete verb (compila) and resource (catálogo y métricas de la biblioteca online de Markdown de doctrina) plus the outputs it produces (paquetes para Hugging Face, GitHub y Google Drive). It is specific and distinguishable, though it never differentiates itself from any sibling tool or explains the relationship to the huggingface_* / doctrina_* family.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from the description whether this is a routine sync, a publish step, or something that should run only after ingesta de documentos.

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