Skip to main content
Glama
Sign In
mcp-morning-brief

mcp-morning-brief

by jeffereychown-Max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

add_feed

Subscribe to a new RSS/Atom feed by providing its URL. Validates by fetching and parsing the feed before adding.

Instructions

Subscribe to a new RSS or Atom feed URL. Validates by attempting to fetch and parse it.

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": {
      "url": "<url>"
    },
    "name": "add_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
labelNoOptional friendly name (defaults to feed title)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The description reveals that the tool validates the URL by fetching and parsing, which adds behavioral context. However, it does not detail behavior on validation failure, idempotency, or authorization requirements. With no annotations, this is partially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the purpose and provide a key behavioral note. No extraneous content.

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?

Missing essential details: return value on success/failure, error handling, behavior if feed already exists, and authentication. No output schema or annotations further limit completeness for a mutation tool.

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 coverage is 50% (only 'label' has a description). The description adds that the URL is a feed URL but does not fully compensate for the undocumented 'url' parameter, failing to specify accepted formats or protocols.

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?

The description clearly states the tool's action: subscribe to a new RSS or Atom feed URL. It distinguishes from sibling tools like list_feeds and remove_feed by indicating it adds a new feed.

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

Usage Guidelines3/5

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

The description implies when to use (when adding a new feed) but lacks explicit guidance on when not to use, prerequisites, or alternatives among siblings.

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

Deploy Server

Other Tools