SiteCheck Web Intel

gCaptain maritime news from its public RSS feed

search_gcaptain_maritime_news

Read-only

gCaptain maritime news from its public RSS feed (keyword filter on title/summary/categories). Latest items only. Public feed, no key. Related tools on this server, for a different need: search_bbc_news_articles when you need BBC News top stories from the public BBC RSS feed; search_news_across_the_web when you need to search news across the web in one call: Google News RSS. 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_gcaptain_maritime_news"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Words that must all appear in the title or summary (optional, max 200 characters)
`limit`	No	How many items, 1 to 30 (default 10)

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real operational context: no API key needed, latest-items-only recency behavior, the filter's target fields, and an explicit cost model ($0.002 USDC per successful call via x402 on Base/Solana/Arc, failed calls free). That pricing and failure-charging detail is exactly the kind of behavior an agent needs before calling.

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?

Front-loaded with purpose and scope before the alternatives and pricing. Every clause carries information, though the 'Related tools on this server, for a different need:' scaffolding and the pricing sentence are somewhat verbose for the payload they deliver.

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-value explanation is unnecessary. The description covers access model (public feed, no key), recency, filter semantics, alternatives, and payment terms — everything needed to decide and invoke correctly for a two-optional-parameter search tool.

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%, so the baseline is 3, but the description adds a meaningful clarification the schema omits: the keyword filter also applies to categories, not just title or summary as the schema states. It does not add format or syntax guidance beyond that, so it stops short of a 5.

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 resource (gCaptain maritime news) and its source (public RSS feed), plus the scope of the keyword filter (title/summary/categories) and the recency constraint (latest items only). It also names the sibling tools it is not, so an agent can distinguish it from search_bbc_news_articles and search_news_across_the_web 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 Guidelines5/5

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

Explicitly routes the agent: use this for gCaptain maritime news, use search_bbc_news_articles for BBC top stories, use search_news_across_the_web for cross-web Google News search. The 'latest items only' note further delimits when this tool is appropriate.

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?