Skip to main content
Glama

BlackLabel Tech Website MCP

read_page

Read-onlyIdempotent

Read one https://blacklabeltec.com page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.

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": {
      "url": "<url>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: the 40,000-character cap and the two output renderings, which matter for large pages. However, it never explains how the Markdown vs. stripped-text mode is selected (there is no corresponding parameter) or what happens at truncation.

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 sentence, front-loaded with the verb and resource, with the character cap placed at the end where it reads naturally. The 'Cloudflare Markdown for Agents' parenthetical is mildly incidental but still informative rather than filler.

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 does well to state the return representation and size limit. It leaves gaps that matter for a fetch tool: truncation signaling, whether partial content is still usable, error behavior for out-of-scope URLs, and how the rendering mode is chosen.

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 0% with a single 'url' parameter, so the description must carry the semantics. It does partially: it restricts the URL to https://blacklabeltec.com pages, which is real meaning beyond the bare 'uri' format. It says nothing about whether subpaths, query strings, or redirects are valid, and offers no example URL.

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 and resource ('Read one ... page') and constrains scope to a single site plus the two possible renderings (Markdown or stripped text). It implicitly contrasts with the sibling search_pages by emphasizing 'one' page, but never names the sibling, so differentiation requires inference.

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 only implied: an agent can infer this is for fetching the full content of a known URL, versus search_pages for discovery. There is no explicit 'use this when...' statement, no mention of when to prefer site_info or search_pages, and no note about whether the URL must already be discovered.

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