Skip to main content
Glama

Search Articles

search_articles
Read-onlyIdempotent

Search the article archive by keyword (headline, summary, key facts, entities, tickers). Use get_latest instead for the newest articles without a query; open a hit's full text with get_article (the slug comes from the search results). Matching is a case-insensitive substring match of the whole query against each article's headline, summary, key facts, entities, and tickers — not a semantic search; headline matches rank first, then newest first. An empty query returns an error. count is the number of articles returned. Returns {query, count, articles} with the same brief shape as get_latest. Behaviour: read-only and public — no authentication or API key; served from the site's published article files, and every call is logged in aggregate (tool name, query, result count, coarse client class; no IP addresses).

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": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-20, default 10).
queryYesKeyword or phrase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds genuinely new behavior beyond those annotations: substring (not semantic) matching, headline-first then newest-first ranking, an empty-query error, the aggregate logging policy, no authentication, and the return shape. Missing logging/no-auth details would have been a gap given the mutation-free public read context, so this is well above bare annotation coverage.

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 before alternatives, ranking, and caveats, and nearly every sentence carries information. It is dense for a single paragraph and the logging sentence is somewhat tangential, but nothing is redundant with the annotations or schema beyond a brief 'read-only and public' restatement.

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?

No output schema exists, yet the description names the return shape ({query, count, articles}) and its relation to get_latest, plus ranking and error behavior. That covers everything needed to call and interpret this two-parameter search tool correctly.

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 coverage is 100%, so both parameters are already documented ('Keyword or phrase', 'Max results (1-20, default 10)'). The description clarifies that the query is matched as a case-insensitive substring across the listed fields rather than semantically, which is meaningful extra semantics, but it does not add constraints (or guidance) for the limit parameter beyond the 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 the article archive by keyword) and names the searched fields (headline, summary, key facts, entities, tickers). It explicitly distinguishes itself from the get_latest and get_article siblings, so an agent can choose 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?

Gives explicit when-to-use guidance for two alternatives: get_latest for the newest articles without a query, and get_article to open a hit's full text, noting the slug comes from the search results. It also names a failure case (empty query returns an error).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.