Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

timesofisrael_headlines

Read-only

Current The Times of Israel headlines for one public section; section must come from timesofisrael_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "timesofisrael_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesTimes of Israel section slug. Documented values: israel-and-the-region, israel-inside, jewish-times, real-estate-israel, tech-israel.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"Times of Israel section slug. Documented values: israel-and-the-region, israel-inside, jewish-times, real-estate-israel, tech-israel."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that results are 'current' headlines limited to a single public section, but says nothing about pagination, result count, or ordering, which matters for a headline-list tool.

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?

A single front-loaded sentence with the resource, scope, and constraint packed in; every clause earns its place.

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?

An output schema exists, so return values need not be explained. The description covers what it returns and the input constraint, leaving only minor gaps (result volume/pagination) that the output schema partly compensates for.

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?

Schema coverage is 100% and the parameter (section slug) is fully documented there, so the baseline would be 3. The description adds the constraint that the value must originate from timesofisrael_sections, which is real semantic guidance beyond the schema's listed slugs.

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?

The description names a specific verb+resource (current headlines) scoped to one public section of The Times of Israel. It explicitly differentiates from the sibling timesofisrael_sections by saying the section value must come from there, so an agent can distinguish the two tools without opening a 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 states the prerequisite that the section must come from timesofisrael_sections, which routes the agent to the correct sibling first. It does not, however, give explicit when-not guidance or mention alternatives beyond that one retrieval step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources