Fetch current TheJournal.ie section headlines by section slug, returning each story’s type, summary, and image when available.
Get TheJournal.ie section headlines. Returns current headlines from one public TheJournal.ie section listing page, with the story type label, summary and image when the page shows them.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | TheJournal.ie section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the transparency burden. It discloses that this is a read-only retrieval of current headlines from one public section listing page and names the returned fields (story type label, summary, image) with the conditional caveat 'when the page shows them'. It omits rate-limit/error behavior, but that is not essential for this simple public read tool.
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?
Two sentences with no filler: the verb and scope are front-loaded, and the conditional return-field detail follows in the second sentence. Every word contributes to selecting or invoking the tool.
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?
For a one-parameter, enum-constrained tool with no output schema, the description is reasonably complete: it identifies the source, scope, and returned content. It could specify the exact shape of the returned headline list (e.g., whether article links are included), but this is a minor gap for a simple listing tool.
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?
The schema already fully covers the single section parameter with a type, description ('TheJournal.ie section slug'), and enum of valid slugs. The description adds no parameter-level semantics beyond the tool name, so the schema-heavy baseline of 3 is appropriate.
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 uses a specific verb and resource ('Get TheJournal.ie section headlines') and clarifies it returns the current listing from one public section page. It is clear about what the tool does, but it does not explicitly differentiate it from sibling tools like thejournal_news or thejournal_sections, so it stops short of a 5.
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?
Usage is implied: call it when you want current headlines for one TheJournal.ie section, and the required section parameter makes that obvious. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives for article details or broader news lists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.