Fetch current headlines from a chosen Khaleej Times section by providing its section slug, returning structured JSON for top-level and sub-section news.
Get Khaleej Times section headlines. Returns fresh headlines from one public Khaleej Times section (top-level sections and sub-sections).
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Khaleej Times section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It communicates that the operation returns data ('Returns fresh headlines'), implies read-only behavior, and notes that the section is public. It does not mention pagination, response format, or rate limits, but for a simple read-only headline fetcher this is acceptable though not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with zero waste. The core action is front-loaded, and the second sentence adds useful scoping detail about freshness, publicity, and section granularity. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple: one required parameter, no output schema, no annotations. The description tells the agent what it returns (headlines) and the scope (one section), which is adequate for basic invocation. However, the absence of an output schema means the description could have specified whether headlines are returned as a list of strings, objects with titles, or include article links.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (the only parameter is described as 'Khaleej Times section slug'), so the baseline is 3. The description adds the note that sections include top-level and sub-sections, which slightly clarifies the enum structure. It does not meaningfully explain slug semantics beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get Khaleej Times section headlines.' It further scopes the tool to 'one public Khaleej Times section (top-level sections and sub-sections),' which helps an agent understand exactly what is returned. However, it does not explicitly distinguish this from sibling tools like khaleejtimes_news or khaleejtimes_sections, so it is clear but not maximally differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context: use this tool to fetch fresh headlines from a specific Khaleej Times section, whether top-level or sub-section. It provides no exclusions or alternative routing to related tools, but the intended scenario is clear enough for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.