Skip to main content
Glama

RSS 2.0 channel export

bpj_rss_channel_export
Read-onlyIdempotent

Generate RSS 2.0 XML with channel description and permalink GUIDs for entries.

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": {
      "name": "<name>",
      "url": "<url>",
      "description": "<description>",
      "entries": "<entries>"
    },
    "name": "bpj_rss_channel_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
entriesYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new information about output construction: the channel description is embedded and entry GUIDs are derived from permalinks (permanent, stable identifiers). It omits anything about how the XML is returned or whether the permalink GUID is generated automatically from the entry URL.

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?

A single well-formed sentence with the output format front-loaded and no filler. It is efficient, though the economy comes partly at the cost of the missing parameter detail rather than through disciplined editing.

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

Completeness2/5

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

With four required parameters, zero schema description coverage, and no output schema, the description should explain the entry encoding and where the generated XML goes. None of that is present, so an agent must guess the pipe-delimited entry format and the return shape before it can call the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0% across four required parameters, so the description must carry the load and largely does not. The critical 'entries' parameter is a 3000-character pipe-delimited 'Title|permalink' string, a format an agent can easily get wrong, and the description never mentions the delimiter, ordering, or that multiple entries are packed into one string; 'url', 'name', and 'description' are only loosely alluded to.

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 output format ("Generate RSS 2.0 XML") plus the resource being described, so an agent knows this produces a feed document. It does not explicitly differentiate itself from the sibling bpj_json_feed_channel or the other exporters, leaving the format choice to be inferred from the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative for producing a feed versus JSON or other export formats. Usage is only implied by the nouns 'RSS 2.0' and 'channel'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.