Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alcom_sections

List AL.com's editorial sections—news, sports, and life—with slugs, names, and URLs to select valid section values for headline queries.

Instructions

Get AL.com editorial sections. Lists the three top-level editorial sections in AL.com's navigation: news, sports and life. Each has a slug, a display name and the section's page url, and the slugs are the values alcom-headlines accepts for section.

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": "alcom_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose the return shape (slug, name, url) and that the result set is exactly three items. It reads unambiguously as a read-only static lookup. It could be more explicit that this is read-only and takes no input, but the disclosure is strong for a no-arg getter.

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?

Front-loaded with the purpose, then the enumerated contents and the downstream linkage, in a tight paragraph with no redundant sentences.

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?

No output schema exists, so the description compensates by naming the returned fields and cardinality, and links the output to the consuming sibling tool. Nothing needed to call it correctly 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, so baseline is 4. The description adds value by explaining what the emitted slugs mean and where they are consumed (alcom_headlines `section`), which is more than the empty schema provides.

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+resource ("Get AL.com editorial sections") and goes further by enumerating the exact three sections (news, sports, life) and the fields each carries. An agent can distinguish this from sibling alcom_headlines/alcom_news without opening anything.

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 final clause explains that the slugs are the values alcom_headlines accepts for `section`, which effectively tells the agent when to call this tool (to resolve valid section values). It stops short of explicitly framing when-not to use it, but the routing context is clear.

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