Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailycaller_sections

List the 22 Daily Caller section slugs accepted by the headlines endpoint, each with its name and page URL, to choose valid sections for news queries.

Instructions

Get The Daily Caller sections. Lists the 22 Daily Caller section slugs that the headlines endpoint accepts, from politics and world to opinion and video, each with its name and section page url. Sponsored content is not offered. A few sections such as satire, two-sides and video publish rarely, so their newest items can be months old.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does reasonably well: it discloses the exact count (22), the returned fields (`name` and section page `url`), that sponsored content is excluded, and that low-volume sections like `satire` and `two-sides` may have items months old. That staleness caveat is genuinely useful and not derivable from structured fields. It doesn't discuss rate limits or error behavior, keeping it out of 5 territory.

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: purpose and scope first, then the return shape, then two practical caveats (no sponsored content, sparse sections). Every sentence adds information an agent would otherwise have to discover by calling the tool.

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?

For a zero-parameter enumeration endpoint with no annotations and no output schema, the description covers what the tool returns, how many items, what is excluded, and a data-freshness warning. Nothing an agent needs before calling it 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?

The tool takes zero parameters, so the baseline of 4 applies. The description appropriately spends its words on the returned shape instead, and adds no misleading parameter talk.

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 The Daily Caller sections') and immediately pins down the scope: the 22 slugs the headlines endpoint accepts, with example values (`politics`, `world`, `opinion`, `video`). This clearly separates it from dailycaller_headlines and dailycaller_article without needing 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 phrase 'slugs that the headlines endpoint accepts' tells the agent this is the discovery step that supplies valid section values for dailycaller_headlines, which is real routing guidance. It stops short of an explicit 'call this before headlines' instruction or a statement of when not to use it, so it lands at a strong 4 rather than 5.

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