Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailykos_sections

List all 24 Daily Kos categories accepted by headline tools, including nested slugs like news/elections, with slug, name, and URL for building valid section queries.

Instructions

List Daily Kos categories. Lists the 24 Daily Kos categories accepted by dailykos-headlines, including nested slugs such as news/elections and news/whitehouse. Each entry has the slug, display name and category url. Dynamic tag archives are not part of this set.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it states the result is a fixed set of 24 (not open-ended), that excludes dynamic tag archives, and that entries are static slugs. It doesn't mention caching/refresh behavior, but for a static taxonomy list that 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?

Purpose is front-loaded in the first sentence and the remaining sentences add distinct value (count, nested slug example, return fields, exclusion). The opening 'List Daily Kos categories' / 'Lists the 24 Daily Kos categories' is mildly repetitive, keeping it out of the top band.

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, and the description compensates by naming the returned fields (slug, name, url) and the count. Nothing an agent needs in order to call and use this zero-parameter tool 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 there is nothing to disambiguate and the schema is empty by design. The description correctly spends no space on nonexistent parameters; baseline 4 applies.

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+resource ('List Daily Kos categories') with concrete scope: exactly 24 categories, nested slugs like `news/elections`, and explicit exclusion of dynamic tag archives. An agent can distinguish it from dailykos_headlines and dailykos_news without opening anything else.

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?

It ties the output to the consuming tool ('categories accepted by `dailykos-headlines`'), implying this is the discovery step before fetching headlines, and it excludes dynamic tag archives. It stops short of an explicit 'use this before calling dailykos-headlines' instruction, so it is clear but not fully prescriptive.

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