Skip to main content
Glama

Markdown Link Index

index_reference_docs

Indexe les titres Markdown et localise les liens relatifs cassés par fichier et ancre.

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": {
      "fichiers": "<fichiers>"
    },
    "name": "index_reference_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
fichiersYesChemin relatif du fichier → contenu Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the tool is read-only, what form the result takes (a report? a map?), whether files are read from disk or only from the supplied content, or what the 2MB-per-file limit implies. 'Par fichier et ancre' hints at result granularity but is far from sufficient.

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?

A single compact sentence with no filler, and the core action is front-loaded. It is efficient, though the brevity contributes to the informational gaps noted elsewhere.

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?

The tool accepts a nested object of files and has no output schema, so the description should explain what the agent gets back — a broken-link list, per-file anchors, etc. It also omits any statement about side effects or size limits. For this complexity level with no annotations and no output schema, the definition is materially incomplete.

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 coverage is 100% and the single parameter is fully documented in the schema as a relative-path → Markdown-content map. The description adds nothing beyond the schema about the parameter, so the 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 specific verb and resource pair: indexing Markdown headings and locating broken relative links, with the scope qualified as 'par fichier et ancre'. An agent knows exactly what analysis it performs, though the dual nature (heading index + link validation) is not clearly separated.

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?

No when-to-use guidance, no prerequisites, and no indication of when this should be preferred over other approaches. With no sibling tools listed, the absence of alternatives is forgivable, but there is still zero contextual framing for invocation.

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.

Resources