Skip to main content
Glama

Black Label Bots Website MCP

search_pages

Read-onlyIdempotent

Find pages on blacklabelbots.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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely new behavioral context beyond them: matching is against URL paths from a sitemap rather than page content, and results come back as URLs accompanied by a match score. It omits ranking order, pagination, and whether matches are partial/case-insensitive, which keeps it from a 5.

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?

Two tight sentences with zero filler; the search scope is front-loaded and the return shape follows immediately. Nothing could be removed without losing information.

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 two-parameter read-only search tool with a complete annotation set, this is nearly sufficient — scope, mechanism, and return shape are all covered without an output schema. The remaining gap is the meaning and bounds of 'limit' and the ordering of returned results.

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 description coverage is 0%, so the description must carry the load. It clarifies that 'query' is words matched against URL path segments (not full-text), but says nothing about 'limit' — how many results are returned, and whether results are ordered by score. Partial compensation 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?

States a specific verb ('Find'), resource ('pages on blacklabelbots.com') and the matching mechanism ('words in their URL path (sitemap search)'), which clearly separates it from read_page (fetches a page) and site_info (metadata). It stops short of naming a sibling explicitly or stating that it does not search page body content, so it lands just under a 5.

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 'use this to discover a page URL, then use read_page to read it', but the description never says when to prefer it over read_page or site_info. There are no exclusions or prerequisites stated, so the routing decision 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