Skip to main content
Glama

MagReader article discovery

search_articles

Read-only

Find published articles by topic keywords, publisher or publication name. Case and spacing/punctuation in names are normalized. Meaningful query words must match metadata together or an individual passage; this is lexical retrieval, not semantic answer generation. Use publication/publisher filters (name or ID) to exclude other publications. For a question, choose one or two specific topic keywords. Returns public metadata and publisher teasers only, including matches inside paid articles. Follow next with the SAME query and filters to search older archive sections.

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
queryYes
cursorNo
publisherNo
publicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / publication
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / publisher
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: this is lexical retrieval rather than semantic answering, name matching is case/punctuation normalized, results are limited to public metadata and publisher teasers even for paid articles, and continuation is via a 'next' token. These are non-obvious traits an agent could not infer from readOnlyHint/openWorldHint alone.

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?

Purpose is front-loaded and each sentence adds a distinct operational fact (matching semantics, filters, query advice, result scope, pagination). It is dense but not padded, though the number of short clauses makes it slightly crowded.

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?

With no output schema and no parameter descriptions, the description covers return scope (public metadata and teasers) and continuation behavior, which is the essential context for calling it correctly. Cursor mechanics and result ordering remain only loosely specified.

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 description coverage is 0%, so the description must carry the burden; it explains that query words must match metadata collectively or within a passage, that publisher/publication accept names or IDs, and that names are normalized. The cursor parameter is only implied through 'Follow next' rather than described directly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find published articles') plus the matchable fields (topic keywords, publisher, publication name). It does not name the sibling get_article_preview, so differentiation from that tool is left implicit rather than stated.

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?

Gives concrete query-construction advice ('For a question, choose one or two specific topic keywords'), tells how to narrow with publisher/publication filters, and specifies pagination behavior ('Follow next with the SAME query and filters to search older archive sections'). It stops short of explicitly naming an alternative tool or when-not-to-use conditions.

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.

Resources