NicheDB

create_feed

Save a query as a feed (needs a key). Sources, kinds and tags narrow; q is a text match; upcoming keeps only future-dated items.

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": {
      "collection": "<collection>",
      "name": "<name>"
    },
    "name": "create_feed"
  }
}

Input Schema

Name	Required	Description
`q`	No	Text the items must match (optional), e.g. tokio
`lat`	No	Query center latitude; requires long
`bbox`	No	west,south,east,north; west > east crosses the antimeridian
`long`	No	Query center longitude; requires lat
`name`	Yes	Display name for the feed, e.g. Rust releases
`sort`	No	Result order. distance (needs lat and long) puts the nearest first, e.g. "distance"; anything else keeps newest first
`tags`	No	Tags, any one matches (optional), e.g. ["rust", "cli"]
`unit`	No	Default km
`kinds`	No	Item kinds to include (optional), e.g. ["release"]
`public`	No	Listed publicly, true or false, default true
`radius`	No	Default 10; maximum 1000 km
`sources`	No	Source slugs to include (optional), e.g. ["crates"]
`upcoming`	No	true keeps only items dated in the future, e.g. true; default false
`enrichers`	No	Enricher names to show (see list_enrichers), e.g. ["youtube"]; omit for the collection defaults
`collection`	Yes	Collection slug, e.g. games (see list_collections)
`description`	No	One line about the feed (optional), e.g. Every Rust crate release

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 1, 2026

changedInput schema / properties / collection / description

Previous value: -"Collection slug"New value: +"Collection slug, e.g. games (see list_collections)"

changedInput schema / properties / description / description

Previous value: -"Optional"New value: +"One line about the feed (optional), e.g. Every Rust crate release"

changedInput schema / properties / enrichers / description

Previous value: -"Enrichers to show; omit for the collection defaults"New value: +"Enricher names to show (see list_enrichers), e.g. [\"youtube\"]; omit for the collection defaults"

changedInput schema / properties / kinds / description

Previous value: -"Item kinds"New value: +"Item kinds to include (optional), e.g. [\"release\"]"

changedInput schema / properties / name / description

Previous value: -"Feed name"New value: +"Display name for the feed, e.g. Rust releases"

changedInput schema / properties / public / description

Previous value: -"Default true"New value: +"Listed publicly, true or false, default true"

changedInput schema / properties / q / description

Previous value: -"Text match"New value: +"Text the items must match (optional), e.g. tokio"

addedInput schema / properties / sort / description

Added value: +"Result order. distance (needs lat and long) puts the nearest first, e.g. \"distance\"; anything else keeps newest first"

changedInput schema / properties / sources / description

Previous value: -"Source slugs"New value: +"Source slugs to include (optional), e.g. [\"crates\"]"

changedInput schema / properties / tags / description

Previous value: -"Tags, any match"New value: +"Tags, any one matches (optional), e.g. [\"rust\", \"cli\"]"

addedInput schema / properties / upcoming / description

Added value: +"true keeps only items dated in the future, e.g. true; default false"

Changed6 schema fields changedSep 13, 2026

addedInput schema / properties / bbox

Added value: +{
+  "description": "west,south,east,north; west > east crosses the antimeridian",
+  "type": "string"
+}

addedInput schema / properties / lat

Added value: +{
+  "description": "Query center latitude; requires long",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / long

Added value: +{
+  "description": "Query center longitude; requires lat",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / radius

Added value: +{
+  "description": "Default 10; maximum 1000 km",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / sort

Added value: +{
+  "enum": [
+    "id",
+    "published",
+    "updated",
+    "distance"
+  ],
+  "type": "string"
+}

addedInput schema / properties / unit

Added value: +{
+  "description": "Default km",
+  "enum": [
+    "km",
+    "mi"
+  ],
+  "type": "string"
+}

First observedSep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and non-idempotence, so the write profile is covered. The description adds the auth-ish 'needs a key' note, but says nothing about duplicate-name behavior, whether a feed is created disabled, or what identifying handle comes back. It also omits entirely the geospatial query mode (lat/long/bbox/radius/unit), which is a meaningful behavioral facet of this tool.

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?

A single tight sentence with the core action front-loaded and the qualifiers after it. Every clause maps to actual parameters; no padding.

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

Completeness3/5

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

With 16 parameters and no output schema, the description covers only about a third of the surface and ignores the whole location-based feed option, which is the least self-evident part of the tool. The rich schema compensates for most field-level gaps, but an agent gets no sense of what a call returns or what the created feed is identified by.

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; every parameter including sort, bbox, enrichers and collection already has prose and examples in the schema. The description restates a subset (sources, kinds, tags, q, upcoming) without adding syntax or edge-case 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?

States a specific verb and resource ('Save a query as a feed') and previews the filter semantics, which is more than a restatement of the name. It does not differentiate from nearby siblings like submit_feed or follow_feed, so an agent must infer which creation-style tool applies.

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 parenthetical '(needs a key)' hints at a prerequisite, and the clauses about sources/kinds/tags/q/upcoming explain narrowing behavior. However there is no explicit when-to-use/when-not-to-use guidance and no routing toward submit_feed or list_feeds as alternatives.

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

All NicheDB tools Inspect

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.