Skip to main content
Glama

JSON Feed channel builder

bpj_json_feed_channel
Read-onlyIdempotent

Build a JSON Feed 1.1 channel with unique item IDs and text content derived from titles.

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>",
      "items": "<items>"
    },
    "name": "bpj_json_feed_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
itemsYes

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the output conforms to JSON Feed 1.1, item IDs are auto-generated as unique, and content is text derived from titles (implying no HTML content). It still omits what the tool actually returns and how IDs are generated.

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 front-loaded sentence with no filler; the core capability comes first. It is efficient, though the brevity contributes to the parameter gaps rather than balancing them.

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?

Three required parameters, a delimited string input, and no output schema leave the description too thin. An agent knows what the tool produces conceptually but not the exact input formatting conventions or the shape of the returned feed, which is the main failure risk here.

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%, so the description must carry parameter meaning, but it barely does. It hints that items carry titles and IDs, yet never explains the pipe-delimited 'Item ID|title|URL, one per line' input format, the 240/3000 character limits, or whether url/name are the channel-level fields — the most error-prone part of the call is undocumented.

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 ('Build a JSON Feed 1.1 channel') and adds distinguishing specifics: unique item IDs and text content derived from titles. It does not explicitly contrast with the sibling bpj_rss_channel_export (a different feed format), so an agent must infer that distinction from the version label 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, and no mention of the RSS export sibling as the alternative format. Usage must be inferred entirely from the tool name and the '1.1' spec reference.

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.