Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofisrael_headlines

Fetch headlines for one Times of Israel section—Israel and the Region, Israel Inside, Jewish Times, Real Estate Israel, or Tech Israel—and return each article’s title and URL.

Instructions

Get Times of Israel section headlines. Returns the current headlines for one Times of Israel section. section is required and takes one of israel-and-the-region, israel-inside, jewish-times, real-estate-israel or tech-israel. Each item has its title and URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesTimes of Israel section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It implies a read operation via 'Get/Returns' and usefully discloses the return shape ('Each item has its title and URL'), which compensates for the absent output schema, but it says nothing about freshness, auth, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three short sentences, front-loaded with the core purpose and with the required-parameter constraint surfaced early. The first and second sentences overlap slightly ('Get ... headlines' vs 'Returns the current headlines'), which is minor redundancy.

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 simple one-parameter headlines tool with no output schema, the description covers the section constraint, valid values, and the item shape (title/URL), which is enough to call it correctly. It stops short of routing guidance against sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is a documented enum. The description merely restates the enum values already present in the schema and adds no format or semantic detail beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('Times of Israel section headlines') and scopes it to 'one Times of Israel section', which distinguishes it from the article/news siblings. It never names a sibling tool explicitly, so differentiation relies on the name rather than the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no exclusion of alternatives, even though siblings like timesofisrael_news and timesofisrael_sections exist. Scope ('one section') is implied but the agent is not told when this is preferable to another Times of Israel tool.

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