Skip to main content
Glama

BlinkHub Wire

by net.blinkhub
OverviewDiscussionsAdmin

search_articles

Search recent government press releases in one market. Free (does not use quota).

Args:
    market: us, kr, gb, eu, nz or au (see list_markets). kr articles are in Korean —
        search them with Korean keywords (e.g. 반도체, 수출).
    query: keywords; every word must appear in the headline, summary or source agency.
        Leave empty to get the latest articles.
    since: optional date YYYY-MM-DD; only articles published on or after this date.
    limit: number of results to return (1-30).
Returns headline, summary, source agency, publish time and id. Use get_article for full text.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sinceNo
marketYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the zero-quota cost model, that Korean-market articles require Korean keywords, and the exact matching semantics (every word must appear in headline, summary, or source agency). It does not cover auth requirements, rate limits beyond quota, or failure modes, hence a 4 rather than a 5.

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?

The purpose and cost model are front-loaded in the first sentence, and the parameter block is terse with no filler. The Args-style formatting is docstring-flavored rather than prose, but every line earns its place, including the return-fields note.

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?

With no output schema, the description still enumerates returned fields (headline, summary, source agency, publish time, id) and routes to get_article for full text. Combined with full parameter coverage and no annotations to rely on, nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description compensates fully: it enumerates market values (us, kr, gb, eu, nz, au), explains query matching and the empty-query default, gives the since format (YYYY-MM-DD) and inclusive semantics, and states the limit range (1-30). Every one of the four parameters is documented beyond the bare schema.

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 ('Search recent government press releases in one market') with explicit scope, and distinguishes itself from get_article by noting the latter is for full text. An agent can tell what this tool returns without opening the 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?

Points to list_markets for valid market codes and get_article for full article bodies, and explains that an empty query returns the latest articles. It also notes the tool is free and does not consume quota, which helps an agent choose it over metered siblings. It stops short of stating when not to use it, but the context is clear.

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

All BlinkHub Wire 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