Skip to main content
Glama

Feed autodiscovery links

bpj_feed_autodiscovery_links
Read-onlyIdempotent

Generate alternate feed links using the declared RSS, Atom or JSON Feed media type.

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": {
      "feeds": "<feeds>"
    },
    "name": "bpj_feed_autodiscovery_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. Beyond that the description says nothing about what is actually returned (markup snippet vs. structured list), ordering, or handling of multiple feeds, and there is no output schema to compensate.

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?

One short sentence, front-loaded with the action verb and with no filler. It is efficiently written, though its brevity leaves the gaps noted in the other dimensions.

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?

For a tool whose sole parameter is a custom pipe-delimited string and which has no output schema, the description omits both the input encoding and the shape of the result. An agent would have to guess at the string format and at what 'links' are returned.

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 the load. It hints that a media type is involved ('declared RSS, Atom or JSON Feed media type'), but never explains that the single string parameter is pipe-delimited 'Type|title|URL' with a 3000-character cap, which the schema title only vaguely gestures at.

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: 'Generate alternate feed links', plus the media types it handles (RSS, Atom, JSON Feed). An agent knows what it produces, though nothing distinguishes it from the adjacent feed-related siblings such as bpj_json_feed_channel.

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. The only contextual cue is 'using the declared ... media type', which implies it operates on already-declared feeds but does not say when an agent should call this rather than another link or feed tool.

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.