NicheDB

feed_items

Read-onlyIdempotent

What a feed selects, newest first. Page with before_id.

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": {
      "feed": "<feed>"
    },
    "name": "feed_items"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Query center latitude; requires long
`bbox`	No	west,south,east,north; west > east crosses the antimeridian
`feed`	Yes	Feed slug, e.g. new-on-steam (see list_feeds)
`long`	No	Query center longitude; requires lat
`sort`	No	Result order. distance (needs lat and long) puts the nearest first, e.g. "distance"; anything else keeps newest first
`unit`	No	Default km
`limit`	No	Rows to return, integer 1-200, default 30, e.g. 50
`offset`	No	Rows to skip when sort=distance, integer, e.g. 30
`radius`	No	Default 10; maximum 1000 km
`before_id`	No	Keyset cursor: the smallest item id from the previous page, e.g. 81234567; not with sort=distance

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 1, 2026

changedInput schema / properties / before_id / description

Previous value: -"Keyset cursor; cannot combine with distance sorting"New value: +"Keyset cursor: the smallest item id from the previous page, e.g. 81234567; not with sort=distance"

changedInput schema / properties / feed / description

Previous value: -"Feed slug"New value: +"Feed slug, e.g. new-on-steam (see list_feeds)"

changedInput schema / properties / limit / description

Previous value: -"Default 30, max 200"New value: +"Rows to return, integer 1-200, default 30, e.g. 50"

changedInput schema / properties / offset / description

Previous value: -"Distance pagination offset"New value: +"Rows to skip when sort=distance, integer, e.g. 30"

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"

Changed8 schema fields changedSep 13, 2026

addedInput schema / properties / bbox

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

changedInput schema / properties / before_id / description

Previous value: -"Keyset cursor"New value: +"Keyset cursor; cannot combine with distance sorting"

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 / offset

Added value: +{
+  "description": "Distance pagination offset",
+  "type": "integer"
+}

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

B3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior. The description adds two genuinely useful behavioral facts: results come newest first by default, and pagination uses a before_id keyset cursor. It says nothing about result volume, failure modes, or how geo filters interact with paging.

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?

Two short sentences, no filler, with the ordering constraint front-loaded before the paging hint. It is efficient, though the terseness is part of why purpose and usage are under-specified.

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?

With 10 parameters covering geo, distance sorting, limit and offset, this is a moderately complex tool, and the description omits that breadth entirely. The rich schema compensates for most of the parameter gap, but an agent skimming only the description would not know this tool supports distance-based sorting.

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 parameter documentation is already handled. The description reinforces only before_id paging and default ordering; it adds no meaning for the geo, sort, or radius parameters beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"What a feed selects" indirectly conveys that it returns the items belonging to a given feed, and "newest first" states the default ordering. However, it never uses a clear verb like "list" or "return items", and it does not distinguish itself from near-siblings such as recent_items, search_items, or get_item.

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?

"Page with before_id" gives a paging hint, but there is no guidance on when to use this tool instead of recent_items, search_items, or list_feeds. The agent must infer the selection conditions from the name alone.

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.