Skip to main content
Glama

Black Label Real Estate Website MCP

read_page

Read-onlyIdempotent

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

A3.6/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 new facts: the output format and a hard 40,000-character truncation ceiling, which the agent needs to know before treating the content as complete. The one unexplained behavior is how Markdown vs. stripped text is selected, since no parameter exposes that choice, leaving the agent guessing about which form a given call returns.

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 front-loaded sentence with no filler; the scope, format and size limit all arrive before the reader needs them. Nothing in it is redundant with the title or repeats schema fields verbatim.

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?

With no output schema, the description carries the return-value burden and does so by naming both output formats and the truncation limit. It is nearly complete for a one-parameter fetch tool, with the only real gap being whether truncated content can be continued or re-fetched.

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% for the single url parameter, so the description must carry the meaning, and it does add one useful constraint: the URL is expected to be on https://blbestate.com. It says nothing about accepted URL forms (query strings, fragments, trailing slashes) or what error results from a non-matching host, so it only partially compensates 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 and resource ("Read one https://blbestate.com page") plus the return formats (Markdown or stripped text), which clearly separates it from discovery-oriented siblings like search_pages. It stops short of explicitly naming that sibling, so the differentiation is implied by "one page" rather than stated.

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 using search_pages or estate_search to discover URLs first, and no statement about what happens when an out-of-domain URL is passed. The domain in the sentence hints the tool is site-scoped, but nothing tells the agent when this tool is the correct choice over its siblings.

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