Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

p0dcasters: This week's digest so far

p0dcasters_newsletter_preview
Read-onlyIdempotent

[p0dcasters] This week's issue of the weekly digest as it would be built now from the live directory: subject, plain text and, with html: true, the HTML. Shows new to the directory, the most followed this week, long-running shows that published, the busiest networks. Read-only, no recipients; the per-reader unsubscribe link is a placeholder. Rebuilt at most every 15 minutes.

Served by p0dcasters (https://p0dcasters.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": "p0dcasters_newsletter_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoInclude the HTML body too. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover readOnly/idempotent/non-destructive, and the description goes further with non-obvious traits: the 15-minute rebuild cache cadence, that no recipients are involved, and that the per-reader unsubscribe link is a placeholder. That last detail is exactly the kind of caveat an agent could not infer from structured fields.

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?

Front-loaded with the purpose, then the contents, then the behavioral caveats, with no filler sentences. The trailing 'Served by p0dcasters (URL)' line is boilerplate but small and does orient the agent to the source.

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 zero-required-parameter read tool with no output schema, the description supplies the return payload shape and freshness characteristics. Only minor gaps remain, such as digest size or whether an empty directory yields an empty or partial digest.

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?

With a single parameter at 100% schema coverage, the schema already documents the html boolean and its default. The description restates 'with html: true, the HTML' without adding format, size, or cost implications, so the baseline of 3 applies.

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?

States a specific verb and resource (preview of this week's digest) and enumerates exactly what the result contains: subject, plain text, and optionally HTML. The 'as it would be built now from the live directory' phrasing separates it from a stored-issue fetch like p0dcasters_get_newsletter without needing to name it.

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?

Clear context for when this applies: inspecting the current draft digest before it goes out, with 'Read-only, no recipients' signalling it is not a send operation. It stops short of explicitly naming when to prefer a sibling issue-fetch tool instead, so there is no exclusion clause.

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