Skip to main content
Glama
seeker

seeker

by bottercode

find_similar

Discover pages with similar meaning to a given URL, and optionally control the number of results or exclude the source domain.

Instructions

Find pages similar in meaning to the given URL.

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": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
num_resultsNo
exclude_source_domainNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the core intent. It does not say how many results come back, that the source domain is excluded by default, whether the operation is read-only or costs a network crawl, or how similarity is scored.

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?

A single front-loaded sentence with no filler, and the core intent is immediately visible. Its brevity is efficient but crosses into under-specification given the three parameters involved.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a three-parameter tool with zero schema coverage and zero annotations the description is far too thin. An agent cannot determine result-count behavior or the effect of the source-domain exclusion from the definition alone.

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

Parameters1/5

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

Schema description coverage is 0% — the only parameter information is a title and, for two parameters, a default value. The description explains the url parameter only implicitly and says nothing about num_results (count/limit semantics) or exclude_source_domain (what excluding the source domain actually means and why the default is true), leaving both undocumented in every channel.

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 similar in meaning") plus the key input ("the given URL"), which is clearly different from get_contents (retrieve a page) and web_search (query-based lookup). It falls short of 5 only because it does not explicitly name those siblings or state the semantic-similarity scope as a differentiating rule.

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: "similar in meaning" suggests semantic/similarity search as opposed to keyword search, which hints at why one would pick this over web_search. There is no explicit when-to-use or when-not-to-use statement, and no mention of prerequisites such as the URL needing to be reachable or already indexed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools