Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

japantimes_sections

List The Japan Times sections and their slugs, names, and URLs so you can choose valid section slugs for headline queries.

Instructions

Get The Japan Times sections. Lists the 60 sections linked from The Japan Times main navigation, which the headlines endpoint accepts, for example news-japan, business-markets, sports-sumo, culture-film and community-voices. Each entry has a slug, a display name and a section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the return shape (slug, name, url), the count (60), and the data source (main navigation), which is good transparency for a read-only enumeration. It omits any statement about auth, rate limits, or freshness, keeping it below 5.

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 purpose, then scope, then return shape. No filler and every clause contributes information.

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?

With no output schema and no parameters, the description must explain the return values, and it does (slug, name, url) plus the count. An agent has everything needed to call and use this tool correctly.

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 is 4. The description adds value by noting the slugs are consumed by the headlines endpoint, but there are no parameters to document.

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+resource ("Get The Japan Times sections") and immediately elaborates with the exact scope: the 60 sections from the main navigation, with concrete slug examples. Fully distinguishes this from sibling article/headline/author tools.

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?

Explains that these sections are the values the headlines endpoint accepts, which tells the agent this is a lookup/enumeration helper feeding japantimes_headlines. It does not explicitly say when NOT to use it or name the alternative tool directly, so it stops short of a full 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