Skip to main content
Glama

Search the technical blog

search_blog
Read-only

Search the status403 technical write-ups on antibot systems, TLS fingerprinting, reverse engineering, scraping, and automation architecture. Returns matching posts with their title, date, tags, excerpt, and URL — pass a returned path to read_page for the full text. Omit the query to get the most recent posts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_blog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many posts to return, most relevant first.
queryNoWords to search for in titles, tags, excerpts, and post bodies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description adds real value by enumerating the return fields (title, date, tags, excerpt, URL) and by disclosing what an omitted query does. It stops short of describing result ordering or pagination beyond the limit parameter, which is a minor gap for an otherwise safe read tool.

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?

Three sentences, front-loaded with the search scope, followed by return shape and the sibling handoff. No redundant or filler text; every clause carries either scope, return information, or usage routing.

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, but the description compensates by listing returned fields, and the optional-query behavior is covered. For a two-parameter read-only search tool this is everything an agent needs to call it correctly.

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 coverage is 100%, and the description still adds meaning beyond it: the empty-query behavior is not expressible in the schema and the field list clarifies what 'query' actually matches against. The limit parameter's ordering semantics ('most relevant first') are already in the schema, so the description adds only modestly.

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?

Names a specific verb (search) and a well-scoped resource (status403 technical write-ups on antibot systems, TLS fingerprinting, reverse engineering, scraping, automation architecture). It also distinguishes itself from the sibling read_page by describing read_page as the full-text follow-up step.

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 three concrete usage conditions: search with a query, omit the query for most recent posts, and pass a returned path to read_page for full text. The handoff to the sibling is explicit, so an agent does not need to infer which tool to chain next.

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