NicheDB

recent_items

Read-onlyIdempotent

Newest items, optionally narrowed to a collection, source or kind.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_items"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Query center latitude; requires long
`bbox`	No	west,south,east,north; west > east crosses the antimeridian
`kind`	No	Item kind, e.g. release, title, filing (optional)
`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
`source`	No	Source slug, e.g. steam-new-releases (see list_sources)
`before_id`	No	Keyset cursor: the smallest item id from the previous page, e.g. 81234567; not with sort=distance
`collection`	No	Collection slug, e.g. games (see list_collections)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / collection / description

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

changedInput schema / properties / kind / description

Previous value: -"Item kind"New value: +"Item kind, e.g. release, title, filing (optional)"

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"

changedInput schema / properties / source / description

Previous value: -"Source slug"New value: +"Source slug, e.g. steam-new-releases (see list_sources)"

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.1/5.0

Behavior3/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 and the description needn't repeat it. The description adds nothing about pagination (before_id keyset cursors), default page size, or the interaction between sort=distance and lat/long/radius, which are the behaviors an agent is most likely to get wrong.

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?

A single front-loaded sentence with no filler and the primary ordering stated first. It is efficient, though its brevity contributes to the omissions in the other dimensions rather than being purely a virtue.

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?

This is a 12-parameter tool with an entire geospatial capability (lat/long/radius/bbox/unit, distance sorting) that the description never mentions, plus no output schema to fall back on. An agent reading only the description would not know this tool can do proximity queries or that it is paginated via before_id.

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 every one of the 12 parameters is documented in the schema itself, including enums, defaults, and the antimeridian note for bbox. The description only echoes collection/source/kind and adds no meaning beyond the schema, so the baseline 3 applies.

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 clear resource and ordering ("newest items") plus the optional narrowing dimensions, so an agent knows it is a recency-ordered listing tool. It does not differentiate itself from siblings like search_items, feed_items, or match_items, which is the only thing keeping it from a 5.

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?

The description offers no when-to-use guidance and names no alternative. With search_items, feed_items, match_items, and upcoming all returning items, an agent has to infer that this one is for unfiltered recency browsing rather than keyword search.

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.