Skip to main content
Glama

Markdown outbound hosts

bpj_markdown_outbound_domains
Read-onlyIdempotent

Count hostnames of absolute HTTP and HTTPS inline links, excluding image targets.

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_outbound_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral scoping beyond that: only absolute HTTP/HTTPS schemes count, only inline links (implicitly excluding reference-style definitions), and image targets are skipped. What remains undisclosed is the shape of the result and whether reference-style links are definitively excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly written sentence with the counting scope front-loaded and the image exclusion trailing as a qualifier. No filler, no restatement of the tool name.

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 carries the burden of explaining what comes back, and it does not — an agent cannot tell whether it receives an integer total, a hostname-to-count mapping, or an ordered list. It also omits the 6000-character input cap. The counting rules themselves are complete enough for correct invocation.

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?

There is one required parameter, 'text', with 0% schema description coverage; the schema only supplies a title ('Source text') and a maxLength of 6000. The description never mentions the parameter, its format expectations, or the truncation risk at the length limit. For a single obvious input the meaning is largely self-evident, so this is adequate but not compensating for the coverage gap.

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?

The description gives a specific verb ('Count') and a precisely bounded resource ('hostnames of absolute HTTP and HTTPS inline links'), plus an explicit exclusion ('excluding image targets') that separates it from siblings like bpj_markdown_image_inventory. It falls short of 5 only because 'count hostnames' is ambiguous about whether the result is a total or a per-host breakdown.

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?

Usage is implied by the scope wording: an agent can infer this is for tallying outbound link destinations in a markdown document. However, it never states when to prefer it over related siblings such as bpj_markdown_reference_coverage or bpj_markdown_internal_fragments, nor does it state that relative/internal links are out of scope.

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.