Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

engadget_sections

Lists all 48 Engadget categories accepted by engadget-headlines, with slug, name, and feed URL. Use it to find valid section slugs before requesting headlines.

Instructions

Get Engadget sections. Lists the 48 Engadget categories accepted by engadget-headlines, such as ai, cybersecurity, smartphone-reviews, space and xbox. Each entry has the slug, display name and category feed url. Categories with an empty feed are not listed.

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 full burden, and it does disclose the return shape (slug, name, feed url) plus a behavioral filter rule ('Categories with an empty feed are not listed'). It doesn't state read-only safety explicitly, but a 'get/list' of a fixed 48-item catalog leaves little ambiguity.

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 sentences, front-loaded with the purpose, then examples, then return shape and the exclusion rule. Every sentence adds information with no padding.

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, the description must describe return values, and it does precisely (slug, display name, feed url) and notes the 48-item fixed scope and the empty-feed exclusion. Nothing an agent needs to call or consume this tool is missing.

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 per calibration the baseline is 4. The description correctly implies no arguments are needed.

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 Engadget sections') and immediately disambiguates by naming the sibling it feeds into ('categories accepted by `engadget-headlines`'). An agent can distinguish this from engadget_headlines, engadget_news and engadget_article without opening a schema.

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 tie to `engadget-headlines` makes the use case clear: call this to discover valid category slugs before filtering headlines. It does not explicitly say 'use this before calling engadget-headlines' or note when not to use it, but the context is unambiguous.

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