Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

inquirer_sections

Retrieve the ten Philippine Daily Inquirer sections accepted by inquirer-headlines, including each slug, display name, and URL, to choose valid section values for headline queries.

Instructions

Get Philippine Daily Inquirer sections. Lists the ten Philippine Daily Inquirer sections that inquirer-headlines accepts, from newsinfo to cebudailynews. Each entry has a slug, a display name and the section's url. Takes no parameters.

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, the description carries the full burden and does a reasonable job: it discloses the exact cardinality (ten sections), the value range (from `newsinfo` to `cebudailynews`), the returned fields (`slug`, `name`, `url`), and that it takes no parameters. It doesn't explicitly say the call is read-only or side-effect free, but for a static enumeration that omission 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and resource, then the relationship to inquirer-headlines, then the return shape. Every sentence earns its place and nothing is padded.

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-parameter, no-output-schema lookup tool, the description covers what it returns (slug/name/url) and its scope (ten sections), which is enough to invoke it correctly. A brief note on how it relates to inquirer_news would make it fully complete, but no critical information 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?

There are zero parameters, so the baseline is 4. The description confirms this explicitly ('Takes no parameters'), which removes any doubt an agent might have about needing a section argument.

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 (Get/Lists) and resource (Philippine Daily Inquirer sections), and explicitly ties itself to the sibling that consumes its output: the sections `inquirer-headlines` accepts. An agent can distinguish it from inquirer_headlines, inquirer_news and inquirer_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?

It clearly signals the use case by naming `inquirer-headlines` as the consumer of these slugs, which implicitly tells the agent to call this before headline retrieval. It does not, however, state when NOT to use it or contrast it with inquirer_news/inquirer_article, so it stops short of explicit routing.

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