Skip to main content
Glama
Sign In
PainSpotter MCP Server

PainSpotter MCP Server

by archoor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Blog Posts

list_blog_posts
Read-onlyIdempotent

Retrieve recent blog posts analyzing validated business opportunities: who’s hurting, why now, how to build it, plus an indie-hacker checklist.

Instructions

List recent published PainSpotter blog posts — weekly long-form analyses of validated business opportunities (who's hurting, why now, how to build it, plus an indie-hacker checklist). Free; no API key required.

Args: limit: Number of posts to return, 1-30. Default 10.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context beyond annotations: 'Free; no API key required' and 'recent published' filter. It does not contradict annotations.

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: two sentences and a bullet. It front-loads the purpose in the first sentence. No wasted words.

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?

Given the tool's simplicity (one optional parameter, annotations covering safety, and an output schema), the description covers purpose, parameter semantics, and free access. No missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage (no description for limit), but the description explicitly explains the limit parameter: 'Number of posts to return, 1-30. Default 10.' This adds complete semantic meaning.

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 action: 'List recent published PainSpotter blog posts'. It specifies the resource (blog posts) and scope (recent published), distinguishing it from siblings like get_blog_post (single post) and get_opportunity/query_opportunities (opportunities).

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?

The description mentions it's free and requires no API key, implying low barrier to use. However, it does not explicitly state when to use this tool versus alternative tools like get_blog_post, nor does it provide exclusions or prerequisites.

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

Deploy Server

Other Tools