Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

vu1nz: List Blog Posts

vu1nz_list_blog_posts
Read-onlyIdempotent

[vu1nz] All vu1nz blog posts: supply-chain analysis, release notes, security research. Returns slug, title, date, tags, summary, and URL.

Served by vu1nz (https://vu1nz.com/mcp).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds value beyond them by listing the returned fields (slug, title, date, tags, summary, URL), which matters because there is no output schema; it does not mention volume, pagination, or ordering.

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?

Two short sentences, front-loaded with scope and followed by the return shape; nothing is redundant. The trailing 'Served by vu1nz (https://vu1nz.com/mcp)' line is attribution boilerplate rather than functional information, which slightly dilutes it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless list tool with no output schema, the description covers content scope and return fields, which is largely sufficient. It stops short of stating ordering, result caps, or whether the entire catalog is returned in one call, which an agent would need for planning.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. The description does not claim to accept filters, which is consistent, but adds no parameter meaning because none exists.

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?

States a specific verb and resource ('All vu1nz blog posts') and enumerates the content domain (supply-chain analysis, release notes, security research), so an agent knows exactly what it retrieves. It does not explicitly name the sibling vu1nz_get_blog_post as the single-post alternative, so differentiation is only implied by 'All'.

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 implied: call this to enumerate the whole post catalog. There is no explicit when-to-use/when-not guidance and no pointer to vu1nz_get_blog_post for fetching one post by slug, leaving the choice to inference.

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

All Profullstack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources