Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomsguide_sections

List all Tom's Guide top-level sections, such as ai, reviews, and phones, with slugs, names, and URLs to choose valid verticals for the headlines endpoint.

Instructions

Get Tom's Guide sections. Lists the 22 top-level Tom's Guide content verticals that the headlines endpoint accepts, such as ai, best-picks, how-to, mattresses, reviews, vehicle-tech and phones. Each entry has a slug, a display name and a url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the result shape (each entry has a `slug`, `name`, and `url`) and that the list is a fixed set of 22. It does not mention whether the list is static or requires any auth, but for a trivial read-only enumeration that is minor.

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?

Three tight sentences, front-loaded with the core action, then the count and purpose, then the return fields. Concrete examples earn their space by helping the agent match user intent to a slug.

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

Completeness5/5

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

With no output schema, annotations, or parameters, the description fully covers what an agent needs: what the tool returns (slug/name/url), how many entries, and how they connect to the headlines endpoint.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The listed values (`ai`, `phones`, etc.) describe valid downstream inputs rather than call-time parameters, and there is nothing more the description could add on the parameter side.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Tom's Guide sections') and immediately characterizes the content as the 22 top-level verticals accepted by the headlines endpoint. The concrete slug examples (`ai`, `best-picks`, `how-to`, `mattresses`) let an agent recognize it as a valid-value/enumeration endpoint distinct from siblings like tomsguide_headlines or tomsguide_news.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'the headlines endpoint accepts' strongly implies this tool is a discovery/lookup step used to feed tomsguide_headlines. However, it never states an explicit when-to-use or when-not-to-use condition, leaving the agent to infer the relationship.

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