Skip to main content
Glama
Sign In

NicheDB

by dev.nichedb
OverviewDiscussionsAdmin

submit_feed

Idempotent

Suggest an RSS or Atom feed for the index. No key needed. An admin reviews every suggestion before anything is fetched; approved podcast feeds are handed to rssamplifier, everything else becomes a source here.

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": "submit_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe feed URL, starting with https://
noteNoWhy it belongs here: who publishes it, what it covers (optional)
emailNoWhere to hear back, if you are not sending a key (optional)
collectionNoCollection slug it belongs in, e.g. podcasts (optional; an admin decides otherwise)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / collection / description
      Previous value: -"Collection slug it belongs in (optional; an admin decides otherwise)"New value: +"Collection slug it belongs in, e.g. podcasts (optional; an admin decides otherwise)"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Substantially beyond annotations: it discloses that no API key is required, that nothing is fetched until an admin approves, and that approved podcast feeds route to rssamplifier while others become a source here. That review gate and downstream routing materially shape whether an agent should bother submitting. Missing only what happens on rejection or how soon review occurs.

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?

Three short sentences, front-loaded with the action and scope, then auth, then lifecycle. No sentence is filler: even 'No key needed' answers a precondition an agent would otherwise have to discover from an error.

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?

For a four-parameter public submission tool with no output schema, the description covers the essentials: what is submitted, that no credential is required, and that a human gate blocks fetching. The only gap is the outcome feedback loop (accept/reject notification), which the schema's email field partially implies.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3 and the schema already explains url, note, email, and collection. The description adds marginal value by hinting at the keyless path (echoing the email field) and noting an admin may override collection, but it adds no syntax or format detail beyond the schema.

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?

'Suggest an RSS or Atom feed for the index' gives a specific verb (suggest, not create) and resource, and the word 'suggest' implicitly separates it from create_feed. It stops short of naming create_feed or add_source outright, so the agent must infer the distinction from 'an admin reviews every suggestion.'

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?

'No key needed' signals the unauthenticated/public case, which is the main reason to pick this over create_feed. However, it never explicitly states when to use this versus create_feed or add_source, nor any exclusion such as already-indexed feeds.

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

All NicheDB 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