Skip to main content
Glama

Ahmed Shaikh's Blog

Search blog posts

search_posts
Read-onlyIdempotent

Full-text search across every blog post (title, description, headings, FAQs and body). Returns the best matches with URL, date, description and a snippet around the match.

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 5).
queryYesSearch terms, e.g. "sql injection" or "CVE-2026-109618".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description usefully adds what is returned (URL, date, description, snippet around the match), which matters because there is no output schema, but it omits result ordering rules and behavior on empty results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the search scope is front-loaded before the return-value summary. Every clause carries information an agent can act on.

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?

For a two-parameter search tool with rich annotations but no output schema, the description covers both the search surface and the shape of results, which is the main gap it needed to fill. Only minor omissions remain, such as ranking behavior and empty-result handling.

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%, with the query and limit parameters fully documented in the schema including bounds and examples. The description adds no syntax, matching-operator, or ranking details beyond what the schema already provides, so the baseline of 3 applies.

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?

The description states a specific verb+resource (full-text search across blog posts) and enumerates the searched fields (title, description, headings, FAQs, body). 'Full-text search' contrasts implicitly with the sibling list_posts and get_post, though neither is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for keyword matching rather than listing or fetching a single post. There is no explicit when-to-use guidance, no mention of when to prefer list_posts, and no note on what happens with zero matches.

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