Skip to main content
Glama

Ace Website MCP

read_page

Read-onlyIdempotent

Read one https://ace-bl.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.7/5.0
Behavior4/5

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

The annotations already cover readOnly, idempotent, openWorld and non-destructive behavior, so the bar is lower. The description still earns credit for adding real context the annotations cannot: the domain restriction to ace-bl.tech, the dual Markdown/text extraction path, and the 40,000-character ceiling. It stops short of saying whether that ceiling causes truncation, an error, or pagination.

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 front-loaded sentence with zero filler; the domain, return format and size cap are all delivered up front. Slightly dense with parenthetical detail, but nothing is wasted.

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 definition covers what an agent needs: scope, domain restriction, extraction mode, and size limit. Edge cases (off-domain URL handling, truncation semantics, redirects) are the remaining gaps.

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% — the single url parameter has only a generic uri format and no description — so the description must compensate. It does add the important constraint that the URL must be an ace-bl.tech page, which is not expressed anywhere in the schema, but gives no other detail on URL form (path, query strings, redirects).

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 — 'Read one https://ace-bl.tech page' — plus the two return formats (Markdown via Cloudflare Markdown for Agents, or stripped text) and a size cap. That is enough to tell it apart from a search-style sibling, though it never explicitly says how it differs from search_pages or site_info.

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?

'Read one page' implies a single-page fetch rather than a site crawl or search, which is implicitly the right context. But there is no explicit when-to-use statement, no pointer to search_pages for discovery, and no guidance on what to do when the page exceeds 40,000 characters.

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