Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wccftech_sections

List all non-empty public Wccftech category and topic sections, plus Reviews, Videos, How To, and Roundups archives, to get slugs for headline queries.

Instructions

Discover Wccftech sections. Lists all non-empty public category and topic sections, plus the Reviews, Videos, How To, and Roundups archives. Use a returned slug with wccftech-headlines; taxonomy values are refreshed from the public WordPress REST API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool lists non-empty public sections and archives, and that taxonomy values are refreshed from the public WordPress REST API, which adds useful freshness and scope context. It still does not explicitly state read-only safety, pagination, or return shape, but the vocabulary clearly implies a read/discovery operation.

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?

The description is three tight sentences with no filler, and it front-loads the purpose before listing returned content and the sibling handoff. Every sentence contributes to selecting or using the tool correctly.

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

Completeness4/5

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

For a zero-parameter discovery tool with no output schema and no annotations, the description is largely complete: it identifies what sections are returned, the public/non-empty constraint, and how the result is used downstream. It could go one step further by noting the general return structure (e.g., names and slugs), but nothing essential for calling it 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 has zero input parameters, so the baseline is 4. The description does not need to explain parameter semantics, and its only related detail—using a returned slug with wccftech-headlines—is about output handoff rather than input configuration.

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?

The description states a specific verb and resource ("Discover Wccftech sections") and then enumerates exactly what the tool returns: non-empty public category/topic sections plus Reviews, Videos, How To, and Roundups archives. It also distinguishes the tool from the sibling wccftech-headlines by explaining the slug handoff, so an agent can identify its role without opening the 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?

It gives explicit usage context by saying to use a returned slug with wccftech-headlines, which tells the agent what to do after calling this tool. It does not, however, state when not to use it or name alternative discovery approaches, so it stops short of the highest level.

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