Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

inews_sections

Retrieve the 45 i sections accepted by inews-headlines, from home and news to football and money, each with slug, name, and URL.

Instructions

Get i sections. Lists the 45 i sections accepted by inews-headlines, from home and news to football, money and relationships. Each entry has a slug, display name and url. home is the site-wide listing, and low-volume sections such as golf or comedy may hold only one or two items.

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 full burden; it discloses the returned fields (slug, name, url), the item count (45), the meaning of `home`, and a useful caveat that low-volume sections may hold only one or two items. It omits explicit safety/read-only framing, but adds genuine behavioral context beyond structure.

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?

Three front-loaded sentences, each earning its place: purpose, contents/consumer, and the `home`/sparse-section caveat. The example sections add illustration without bloat, though the sentence is somewhat dense.

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?

With 0 params and no output schema, the description must explain the return shape, which it does (slug/name/url) along with cardinality caveats. Complete enough for a simple enumeration tool, though it could note the discovery workflow more explicitly.

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 there is nothing to document; the baseline for a 0-param tool is 4. The description correctly adds no parameter noise.

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 i sections') and immediately clarifies it is the enumeration of the 45 section slugs accepted by `inews-headlines`. The relationship to the sibling tool is explicit, so an agent can tell it apart from inews_headlines and inews_article without opening any 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 naming `inews-headlines` as the consumer of these sections, the description strongly implies this is a discovery step for valid section values. It gives clear context but does not state an explicit 'use this before X' directive or any when-not condition.

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