Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailykos_headlines

Fetch current Daily Kos category headlines by providing a section slug, like news/elections or cartoon. Returns matching story items or an empty list if none exist.

Instructions

Get Daily Kos category headlines. Returns the current stories for one Daily Kos category. section is required and takes one of 24 slugs such as news/elections, news/courts, cartoon or announcements; any other value returns a 400. Some categories can be empty, which comes back as an empty items list.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Kos category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior beyond the schema: an invalid section value returns a 400, and empty categories return an empty `items` list. It does not cover auth requirements, rate limits, or pagination, so it is strong but not exhaustive.

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?

Three tight sentences, front-loaded with the core purpose, then the required parameter and its examples, then edge-case behavior. No filler or redundancy.

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 single-parameter, no-output-schema tool with no annotations, the description covers purpose, the required param, error behavior, and empty-result behavior well. Pagination or result-size expectations for 'current stories' are the only notable omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum already enumerates all 24 slugs, so the description adds little new. It does add value by stating that the parameter is required and that non-enum values produce a 400, plus concrete slug examples, but the enum does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get Daily Kos category headlines') and clarifies scope ('Returns the current stories for one Daily Kos category'). It is clear on its own, but it never distinguishes itself from the sibling tools dailykos_news, dailykos_sections, or dailykos_article, so an agent must guess why it would choose this over them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the reader infers this is for fetching headlines within a single category. There is no explicit when-to-use/when-not guidance and no routing to alternatives, despite three closely related dailykos siblings in the toolset.

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