Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xda_sections

List XDA RSS sections accepted by xda-headlines, including news, reviews, buying guides, GPU, laptops, and AI tools. Returns each section's slug, display name, and feed URL.

Instructions

Get XDA RSS sections. Lists the XDA sections accepted by xda-headlines, including news, reviews, buying-guides, gpu, laptops, gaming-handhelds, windows, linux-hub and ai-tools. Each has a slug, a display name and a feed url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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. It discloses that the call takes no parameters and describes the returned shape (each entry has a `slug`, display `name`, and feed `url`), which is valuable given there is no output schema. It omits auth/rate-limit context, but for a parameterless read-only listing this 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource, then the enumeration and return-shape note. The long inline list of section slugs is partly redundant with what the tool returns, but it usefully previews the value space, so it mostly earns its place.

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-param, no-output-schema discovery tool, the description covers purpose, consumption relationship, parameterlessness, and return fields. Nothing critical to correct invocation 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?

Zero parameters, which is the baseline-4 case. The description confirms this explicitly ('Takes no parameters'), so there is no ambiguity about how to invoke it.

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?

Specific verb (Get/List) plus resource (XDA RSS sections), and it explicitly ties itself to the sibling `xda-headlines` that consumes these values. An agent can distinguish it from headline/article siblings 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?

By stating the sections are 'accepted by `xda-headlines`' it makes the when-to-use obvious: call this to discover valid section values before calling `xda-headlines`. It stops short of an explicit when-not-to-use or a named alternative flow, so it is clear context rather than full routing guidance.

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