Skip to main content
Glama

List covered websites

list_websites
Read-onlyIdempotent

Websites the catalogue covers, with the number of Actors for each, its page and one MCP URL bundling its main Actors. Filter by part of the name or by category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_websites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoPart of a website name, e.g. 'google'.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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=false, so the safety profile is fully covered by structured data. The description adds value by describing the shape of each returned record (Actor count, page, MCP URL), which matters since there is no output schema, but it says nothing about pagination, the 50-item default, or the 200 cap.

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 sentences with no filler, and the core content (what is returned) is front-loaded before the filtering note. The middle clause 'its page and one MCP URL bundling its main Actors' is slightly compressed and ambiguous in its pronoun reference, but overall the text is efficient.

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 no output schema, the description responsibly explains the returned fields, which is the most important gap it fills. It falls short on the third parameter (limit), pagination behavior, and any indication of result ordering or truncation, which an agent needs to call this correctly at scale.

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 coverage is only 33% — 'query' is documented in the schema and 'category' has an enum of allowed values, but 'limit' is undocumented in both schema and description. The description's mention of filtering by part of the name or by category reinforces the two filter parameters but adds no syntax or format detail beyond what the schema already provides.

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 names the resource (websites the catalogue covers) and enumerates what each entry contains: Actor count, page, and a bundled MCP URL. It is clearly a listing/enumeration tool, distinguishable from siblings like list_categories or search_tools, though it never states the verb explicitly and relies on the tool name for that.

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?

The closing sentence 'Filter by part of the name or by category' implies the two filtering modes, which is useful context for invocation. However, there is no explicit guidance on when to use this versus search_tools or list_categories, and no mention of what happens when no filter is supplied.

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