Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

time_sections

Lists the 10 TIME section slugs accepted by the headlines endpoint, including news, politics, world, business, technology, health, entertainment, sports, ideas, and climate.

Instructions

Get TIME RSS sections. Lists the 10 TIME section slugs that the headlines endpoint accepts: news, politics, world, business, technology, health, entertainment, sports, ideas and climate. Each entry has a slug, a display name and a url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose the cardinality (10 sections) and the exact return shape per entry (slug, name, url). It never explicitly states the operation is a read-only static reference, but the wording makes that unambiguous.

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?

Two sentences, zero waste. The core purpose and the enumeration of valid slugs are front-loaded, and the return-shape clause is tacked on last where it belongs.

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 lookup with no output schema, the description supplies both the enumeration of valid values and the per-entry field list, which is enough for an agent to consume the result without guessing. Adding an explicit read-only note would make it fully complete.

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 and the baseline is 4. The description instead spends its space on the value domain (the ten valid slugs), which is the substitute for parameter semantics here.

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 TIME RSS sections') and immediately scopes it as the slug list 'the headlines endpoint accepts', which distinguishes it from time_headlines, time_news and time_article. An agent can tell what it returns 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?

The description ties the tool to the headlines endpoint, implying it is the prerequisite lookup for section-filtered headline queries. It stops short of an explicit 'use this before calling time_headlines' instruction or any when-not-to-use guidance, but the 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