Skip to main content
Glama

BL Sports Website MCP

read_page

Read-onlyIdempotent

Read one https://michaelbarber.tech 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

A3.9/5.0
Behavior4/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 beyond that: the output is Markdown via Cloudflare Markdown for Agents or a stripped-text fallback, and content is capped at 40,000 characters. It stops short of explaining truncation signaling or error behavior.

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 sentence with no filler; the scope, output format and size cap are all front-loaded. Every clause carries information an agent needs.

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

Completeness4/5

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

For a one-parameter read tool with full annotation coverage and no output schema, the description supplies the domain scope, return representation and length limit. Remaining gaps are minor: no error/not-found behavior and no statement of when the text fallback is used.

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 schema only declares a `url` string with format uri and no description, so the description carries the parameter meaning. It adds the essential constraint that the URL must be a page on michaelbarber.tech, which the schema does not convey. It does not state how off-domain URLs are rejected or how the Markdown-vs-text choice is made.

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?

"Read one https://michaelbarber.tech page" gives a specific verb and a scoped resource, and the domain restriction makes the scope concrete. It implicitly separates itself from search_pages by emphasizing a single page, but it never names the sibling or states the contrast explicitly.

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?

Use is implied by the description: fetch a single known page. There is no explicit when-to-use versus search_pages (find a page) or site_info (metadata about the site), and no note on what happens for pages outside the domain, so routing is left to inference.

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