Skip to main content
Glama

search_articles

Read-onlyIdempotent

Search Aleksei Aleinikov engineering articles (EN/DE) on Google Cloud, Kubernetes/GKE, Cloud Security, Architecture, PostgreSQL, AI/LLM, and Hardware Lab. Use this first to discover articles and obtain valid pillar and slug values before calling read_article; use get_candidate_profile instead for CV/hiring questions, or list_tools for interactive browser utilities. Read-only, unauthenticated, no side effects, uses a 10-minute cached search index, and is subject to a 30 req/min per-IP rate limit. Returns matching article metadata and URLs, or an empty list message when nothing matches.

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
langNoOptional language index ("en" or "de"). Auto-detected from query keywords and German umlauts if omitted.
limitNoMaximum number of ranked results to return (1-15, default 5).
queryYesNon-empty search keywords or topic phrase.

Output Schema

NameRequiredDescriptionDefault
langYesResolved search index language.
countYesNumber of matching articles returned.
queryYesNormalized query string.
articlesYesRanked list of matching articles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Language (auto-detected if omitted)."New value: +"Optional language index (\"en\" or \"de\"). Auto-detected from query keywords and German umlauts if omitted."
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 5)."New value: +"Maximum number of ranked results to return (1-15, default 5)."
    • changedInput schema / properties / query / description
      Previous value: -"Search query keywords."New value: +"Non-empty search keywords or topic phrase."
    • addedInput schema / properties / query / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "articles": {
      +      "description": "Ranked list of matching articles.",
      +      "items": {
      +        "properties": {
      +          "date": {
      +            "type": "string"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "markdownUrl": {
      +            "type": "string"
      +          },
      +          "pillar": {
      +            "type": "string"
      +          },
      +          "readingTime": {
      +            "type": "integer"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "pillar",
      +          "slug",
      +          "url",
      +          "markdownUrl"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "count": {
      +      "description": "Number of matching articles returned.",
      +      "type": "integer"
      +    },
      +    "lang": {
      +      "description": "Resolved search index language.",
      +      "enum": [
      +        "en",
      +        "de"
      +      ],
      +      "type": "string"
      +    },
      +    "query": {
      +      "description": "Normalized query string.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "lang",
      +    "query",
      +    "count",
      +    "articles"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, but the description still adds operationally useful facts the annotations cannot express: unauthenticated access, a 10-minute cached index (staleness), a 30 req/min per-IP rate limit, and empty-list messaging when nothing matches. These are exactly the traits an agent needs to plan retries and rate-limit backoff.

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 the purpose and routing advice before the operational constraints, and every clause carries information. The topical list is slightly long relative to its discrimination value, which keeps it just below a 5.

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?

For a three-parameter read tool with an output schema and rich annotations, nothing an agent needs is missing: discovery workflow position, sibling routing, auth model, caching, rate limits, and empty-result handling are all stated.

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%, including the lang auto-detection rule, limit bounds/default, and non-empty query requirement, so the schema carries the parameter burden. The description adds no format hints (e.g., query syntax, keyword vs. phrase behavior) beyond what the schema already states, so the baseline of 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 ('Search Aleksei Aleinikov engineering articles') and names the topical scope (Google Cloud, Kubernetes/GKE, Cloud Security, Architecture, PostgreSQL, AI/LLM, Hardware Lab) plus the language coverage (EN/DE), which lets an agent tell it apart from get_candidate_profile and read_article without opening 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 Guidelines5/5

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

Gives explicit sequencing ('Use this first to discover articles and obtain valid pillar and slug values before calling read_article') and names two alternatives with the conditions that select them: get_candidate_profile for CV/hiring questions, list_tools for interactive browser utilities. Both when-to-use and when-not-to-use are covered.

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