LaraBench

Search Laravel news and releases

search_laravel_news

Read-only

Search recent Laravel ecosystem news and package releases indexed by LaraBench. Results are limited to the last 7 days. Each item carries a LaraBench detail page and the original article or release notes URL.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items to return.
`query`	No	Free-text search across article and release titles and summaries.
`types`	No	Restrict results to articles, package releases, or both. Defaults to both.
`topics`	No	Topic filters such as laravel, php, vue, jobs, or packages.
`channel`	No	Release channel to include. stable excludes prereleases, preview returns only prereleases, all returns both. Defaults to stable.
`sources`	No	News source filters.
`packages`	No	Composer or npm package filters.
`projects`	No	Project filters such as laravel, inertia, livewire, filament, or pest.

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes	Article and release items are shaped differently; see the type field.
`generatedAt`	Yes
`larabenchUrl`	Yes
`totalAvailable`	Yes
`freshnessWindowDays`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral context beyond annotations: results are limited to the last 7 days and each item includes a LaraBench detail page plus an original URL, which helps set expectations.

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?

Two sentences, front-loaded with the action and resource, no filler. Every clause adds value: the 7-day restriction and the detail/original URL links are the key operational notes.

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 search tool with 8 optional parameters and an output schema, the description supplies the crucial temporal constraint and result item composition. It does not mention default ordering or empty-query behavior, but the open-world annotation and schema compensate for that gap.

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?

The input schema covers 100% of parameters with meaningful descriptions, so the description does not need to repeat parameter-level details. It adds high-level context about time window and result structure, but no additional per-parameter semantics beyond the schema. Baseline 3 is appropriate.

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?

Description states a specific verb and resource: 'Search recent Laravel ecosystem news and package releases indexed by LaraBench.' It clearly distinguishes from the sibling tool search_laravel_jobs by focusing on news/releases rather than jobs.

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?

The description clearly communicates domain scope: Laravel news and releases, not jobs. It does not explicitly mention the sibling tool as an alternative, but the differentiation is evident from the stated resource and 'recent' timeframe.

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

All LaraBench tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

The two tools target distinct domains: Laravel jobs and Laravel news. There is no overlap in purpose, and each tool's description clearly differentiates its scope.

Naming Consistency5/5

Both tools follow the same verb_noun pattern: search_laravel_jobs and search_laravel_news. The naming is perfectly symmetric and predictable.

Tool Count4/5

With only 2 tools, the server is minimal but appropriate for its focused niche of Laravel job and news search. It's slightly thin but not inadequate.

Completeness4/5

The two search tools cover the apparent main functions of the server. A possible gap is lack of direct retrieval by ID, but search results include detail page URLs, making the surface reasonably complete.

Resources

Need Help?