Skip to main content
Glama

Ace Website MCP

search_pages

Read-onlyIdempotent

Find pages on ace-bl.tech 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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile needs no restating. The description adds genuine behavioral context the annotations lack: matching happens against URL paths rather than page content, and results carry a match score. It 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with zero filler, and the domain plus matching surface are front-loaded before the return-value note. 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.

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 search tool with a rich annotation set and no output schema, the description supplies the essential shape of the return value (URLs with a match score). However, the undocumented `limit` behavior and the unspecified match semantics leave gaps an agent would need the schema to close.

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 carries the full burden, yet it only loosely characterizes `query` as "words in their URL path" without stating whether matching is substring, prefix, or token-based. The `limit` parameter (default 20, max 50) is never mentioned, leaving a documented-in-schema-only constraint the agent must discover by opening the schema.

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 ("Find pages") plus the search surface ("words in their URL path (sitemap search)") and the domain ace-bl.tech, which is far more specific than the bare name. It does not explicitly contrast itself with siblings like read_page or site_info, so an agent must infer the find-vs-fetch distinction.

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?

The parenthetical "(sitemap search)" hints at the use case of locating a page when you only know fragments of its URL, but there is no explicit when-to-use, when-not-to-use, or named alternative among read_page, site_info, and list_products. The agent gets no routing guidance beyond 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