Skip to main content
Glama

Black Label Real Estate Website MCP

search_pages

Read-onlyIdempotent

Find pages on blbestate.com by words in their URL path (sitemap search). Returns URLs with a match score.

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": {
      "query": "<query>"
    },
    "name": "search_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real value by disclosing the matching basis (URL path, not page body) and that results carry a relevance score, but says nothing about result ordering, pagination, or what happens when nothing matches.

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?

Two tight sentences with the purpose front-loaded and no filler; the mechanism and return shape are packed into the second sentence. Nothing is redundant, though the parenthetical "(sitemap search)" is a bit jargon-dependent.

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?

For a simple two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, mechanism and return type adequately. It falls short on limit semantics and on how matching/ranking behaves, which matters for an agent deciding how many results to request.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that "query" matches words in the URL path, but the "limit" parameter (default 20, max 50) is entirely undocumented in both description and schema, leaving half the inputs opaque.

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 ("Find pages") plus the matching mechanism ("words in their URL path (sitemap search)") and output shape ("URLs with a match score"). An agent can tell this is a site-page/sitemap lookup rather than a content or data search, though it never names a sibling to contrast with.

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: it fits when you know fragments of a page's URL path. There is no explicit when-to-use/when-not, and no pointer to alternatives among siblings such as estate_search (data search) or read_page (fetch a known page), which an agent must infer.

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