Skip to main content
Glama

Sunset Website MCP

search_pages

Read-onlyIdempotent

Find pages on sunsetmixing.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.5/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 open-world, so safety is covered. The description adds two real facts beyond that — matching is against URL paths and results carry a match score — but says nothing about result ordering, whether the sitemap index is cached or fresh, 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 short sentences with the scope and mechanism front-loaded and the return shape trailing. No redundant restatement of the tool name and no filler.

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?

With only two params and no output schema, the definition is close to sufficient, and it does describe the return value at a high level. It is missing whether the search is token or substring based, how results are ordered, and any freshness caveat for the sitemap index, which an agent would need to interpret empty or noisy 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 parameter meaning. It does explain the important one, clarifying that 'query' matches words in URL paths rather than page content, but it never mentions 'limit' or how score-based ordering interacts with it.

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?

Names a specific verb and resource ('Find pages') plus the target site ('sunsetmixing.com') and the matching mechanism ('words in their URL path (sitemap search)'). It implicitly separates itself from read_page by being a discovery tool, though it never names a sibling explicitly.

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 implied rather than stated: the phrase 'in their URL path' tells the agent this is not full-text page search, which is a useful selecting constraint. There is no explicit when-to-use or when-not-to-use guidance, and nothing directs the agent to read_page for the follow-up fetch or to site_info for site-level questions.

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