SiteCheck Web Intel

Latest Drive.com.au articles: headline, publisher, publish

search_drive_com_au_news

Read-only

Latest Drive.com.au (Australia) articles: headline, publisher, publish time and link, newest first, optionally matching search words, from the last 1-30 days. Found through Google News's public RSS index of drive.com.au (the site blocks automated clients); links are Google News redirect links to the article. Headlines only, no article text. Related tools on this server, for a different need: search_ap_news_articles when you need Latest Associated Press articles: headline, publisher; search_google_news when you need Google News search: headline, publisher, publish time. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_drive_com_au_news"
  }
}

Input Schema

Name	Required	Description
`q`	No	Words to search for within the site (optional, max 150 characters), e.g. Toyota
`days`	No	Only articles from the last N days, 1 to 30 (default 7)
`limit`	No	How many articles, 1 to 100 (default 20)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: discloses the data source (Google News public RSS index because drive.com.au blocks automated clients), that links are Google News redirect links rather than direct article URLs, that only headlines are returned, and the billing model ($0.002 USDC per successful call via x402, failures not charged). Those are exactly the facts an agent needs before calling a metered 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.

Conciseness4/5

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

Well front-loaded: purpose first, then data-source caveats, then alternatives, then price. Dense but every clause carries information; the 'Related tools on this server, for a different need' framing is slightly wordy and could be tightened without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 no explanation, and the description still covers the things structure cannot: why results may be limited (RSS proxy), that links are redirects, that no body text exists, and the payment requirement. Nothing an agent needs in order to call this correctly is missing.

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%, so the schema already documents q, days and limit precisely. The description only restates the ranges ('last 1-30 days', 'optionally matching search words') without adding syntax, matching behavior, or default semantics beyond the schema — baseline 3 applies.

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?

States a specific verb and resource — latest Drive.com.au articles with headline, publisher, publish time and link, newest first. The scope is bounded (site-specific, last 1-30 days, headlines only) so an agent can tell it apart from the generic news siblings without inspecting any 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?

Explicitly routes two related cases elsewhere (search_ap_news_articles for AP, search_google_news for general Google News search) and states the limitation that no article text is returned. Guidance is clear but only covers two of the many publication-specific siblings, so the agent must still infer when this beats e.g. search_reuters_articles.

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

All SiteCheck Web Intel tools Inspect

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

Need Help?