Skip to main content
Glama

Markdown image asset inventory

bpj_markdown_image_inventory
Read-onlyIdempotent

Group simple inline image destinations with alt labels and source line numbers.

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": {
      "text": "<text>"
    },
    "name": "bpj_markdown_image_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description adds almost no behavior beyond that: it does not say what happens to images inside code fences, reference-style definitions, or malformed markup, nor what the grouping output looks like. The single added signal is the implicit limitation to "simple inline" forms, which is too vague to act on.

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 eleven-word sentence with the resource front-loaded and no filler. It is efficient, though its brevity is achieved by omitting content rather than by tight editing, which is penalized under completeness instead.

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?

A one-parameter inventory tool with no output schema and no parameter documentation leaves the description carrying the burden of explaining what is returned – the grouping key, the alt-label handling, and the line-number format. None of that is present, so an agent knows roughly what goes in but not what comes out or how to interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter with 0% schema description coverage; only the schema title "Source text" and a 6000-character cap are given. The description never mentions the input at all – not that it is markdown source, not that it is capped at 6000 characters, and not what happens if the input exceeds that. With coverage this low, the description should compensate and does not.

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?

Names a verb ("Group") and a resource ("simple inline image destinations with alt labels and source line numbers"), which is enough to recognize an image-extraction/listing tool. However, "group" is never defined – grouped by destination? by file section? – and "simple inline" is an undefined qualifier, so the exact output shape stays opaque. It is distinguishable from siblings like bpj_image_alt_check only by inference from the noun 'inventory' in the tool name, not from the description itself.

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 mention of when not to use it, and no pointer to alternatives such as the alt-text checker or other markdown inventory tools. The phrase "simple inline" faintly implies scope (excluding reference-style or HTML images) but never states it, and the agent must guess whether this tool is the right one for a given markdown asset question.

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.