Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

RSSAmp: Directory and crawler status

rssamplifier_directory_stats
Read-onlyIdempotent

[RSSAmp] How big the directory is, what it is made of, and whether the crawler is keeping up. stale is active feeds not read successfully in a day; due is a backlog that should drain within a tick or two. Answer this before concluding a feed is missing — it may simply not have been crawled yet.

Served by RSSAmp (https://rssamp.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": "rssamplifier_directory_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world reach. The description adds behavior the annotations cannot: what 'stale' and 'due' mean and the expectation that backlog drains within a tick or two, which shapes how an agent should interpret and re-poll the result. It does not describe update cadence or freshness of the stats themselves.

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 metric definitions, then the actionable guidance — every sentence does work. The trailing 'Served by RSSAmp (https://rssamp.com/mcp).' line is promotional rather than operational and slightly dilutes an otherwise tight description.

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?

With no output schema, the description carries the burden of explaining returns; it defines the two interpretation-critical fields and frames the aggregate counts at a high level. The exact response shape (which counts are returned) remains unspecified, but an agent can call this zero-parameter tool correctly and interpret the key signals.

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?

The tool takes zero parameters, so the schema-level baseline of 4 applies and there is nothing further to disambiguate.

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 resource and scope: directory size/composition plus crawler health, with two named derived metrics (stale, due). The phrase 'what it is made of' is slightly metaphorical rather than naming the actual breakdown dimensions, which keeps it just short of a 5.

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?

Gives a concrete when-to-use rule: call this before concluding a feed is missing, because it may not have been crawled yet. It does not name or exclude any specific sibling tool, so an agent must infer that feed-level lookups belong to the get_feed/search tools.

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