NicheDB

upcoming

Read-onlyIdempotent

Items dated in the future (releases, launches, deadlines), soonest first.

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

Input Schema

Name	Required	Description
`lat`	No	Query center latitude; requires long
`bbox`	No	west,south,east,north; west > east crosses the antimeridian
`days`	No	How many days ahead to look, integer, default 30, e.g. 90
`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 50, e.g. 20
`radius`	No	Default 10; maximum 1000 km
`collection`	No	Collection slug, e.g. games (see list_collections)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / days / description

Previous value: -"Horizon, default 30"New value: +"How many days ahead to look, integer, default 30, e.g. 90"

changedInput schema / properties / limit / description

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

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"

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 readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds the default result order (soonest first), which is useful, but says nothing about pagination, default look-ahead window, or how the geo filters change results.

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?

One sentence, zero filler, with the resource and the ordering front-loaded. Every clause earns its place.

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?

For a 9-parameter tool with all-optional params and no output schema, the description omits important framing: the default 30-day window, that lat/long/bbox/radius are optional geo filters, and that collection scopes the search. The schema covers these, but the description alone would leave an agent guessing about defaults.

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% and every one of the 9 parameters is documented in the schema, including defaults and constraints, so the baseline is 3. The description adds no parameter-level meaning beyond that.

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 resource and filter: items dated in the future, with concrete examples (releases, launches, deadlines) and the default ordering. It implicitly contrasts with recent_items by scoping to future dates, but never names the sibling, so an agent must infer the split.

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 future-date scope implies when to call it (as opposed to recent_items or search_items), but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is inferred from the noun phrase rather than stated.

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.