Skip to main content
Glama

Auditar cobertura documental

auditoria_conocimiento
Read-onlyIdempotent

Resumen de la cobertura real y calidad de fuentes; no equivale a indexación en buscadores.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety and repeatability need no restating. The description's added value is the interpretive caveat that results reflect real coverage and source quality rather than search-engine indexing — useful for reading the output, but it says nothing about granularity, freshness, or what limits the audit.

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 tight sentence with a semicolon-delimited clarification, no filler or repetition. It is efficiently sized for a zero-parameter tool, though the terseness borders on under-specification rather than crispness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description carries full responsibility for conveying what the audit actually returns, and it only offers two abstract nouns ("cobertura real" and "calidad de fuentes"). An agent cannot predict the shape of the response, what metrics define source quality, or what corpus is covered, which is a material gap for an audit-style tool.

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 no parameters (schema is an empty object with additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-related gaps exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns a summary of "cobertura real y calidad de fuentes," which weakly restates the title "Auditar cobertura documental" rather than naming a concrete output or resource scope. The negation ("no equivale a indexación en buscadores") does help separate it from an index-status tool, but the agent still cannot tell precisely what is being audited or over what corpus.

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?

There is no explicit when-to-use statement or named alternative, but the clause "no equivale a indexación en buscadores" implicitly excludes the indexing-status use case and nudges the agent toward this tool for quality/coverage questions. That is only an implied routing hint, not stated guidance about which sibling to pick instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.