scout-mcp

hashnode_search

Search Hashnode for technical blog posts by tag and keyword. Returns title, brief, reactions, reading time, and author info. Ideal for finding in-depth technical articles.

Instructions

Search Hashnode for technical blog posts. Uses tag-based lookup with keyword filtering. Returns title, brief, reactions, reading time, and author info. Good for in-depth technical articles.

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": "hashnode_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query (used as tag slug + keyword filter)
`per_page`	No	Results per page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, but the description explains behavior: uses 'tag-based lookup with keyword filtering', and returns specific fields. It does not mention rate limits, authentication requirements, or whether results are sorted by relevance, but given the absence of annotations, it provides adequate transparency.

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?

The description is concise (three sentences) and front-loaded with the main action. Each sentence provides distinct information: action, mechanism, output, and use case. No redundant or unnecessary words.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description covers purpose, input, output fields, and use case. It is mostly complete, though it could mention pagination behavior or any sorting details. However, it meets requirements for a straightforward search tool.

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% (both parameters have descriptions). The description adds context that 'query' is used as a tag slug combined with keyword filtering, which is not in the schema. 'per_page' is adequately described in the schema. The description adds moderate value 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?

The description clearly states the tool's purpose: 'Search Hashnode for technical blog posts.' It specifies the input mechanism ('tag-based lookup with keyword filtering') and the output fields ('title, brief, reactions, reading time, and author info'). It also distinguishes itself from siblings by focusing on technical articles and Hashnode specifically.

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?

The description provides clear context on when to use this tool ('for in-depth technical articles') and implies it is specific to Hashnode. However, it does not explicitly state when not to use it or mention alternatives among the sibling tools for other types of content.

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