NicheDB

search_items

Read-onlyIdempotent

Full-text search over titles, summaries and tags. Use this first when you know a name.

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": {
      "q": "<q>"
    },
    "name": "search_items"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search words, e.g. elden ring
`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-100, default 20, e.g. 10
`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.

Changed5 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 / kind / description

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

changedInput schema / properties / limit / description

Previous value: -"Default 20, max 100"New value: +"Rows to return, integer 1-100, default 20, e.g. 10"

changedInput schema / properties / q / description

Previous value: -"Query"New value: +"Search words, e.g. elden ring"

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.8/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 covered. The description adds the searchable fields and a usage preference, but it does not add deeper behavioral details such as ranking logic, result limits, or pagination. A 3 is appropriate given the annotation coverage.

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?

The description is two short sentences with zero wasted words, and the purpose is front-loaded before the usage hint. Every sentence earns its place.

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 search tool with ten optional parameters, rich schema descriptions, and safety annotations, the description gives enough context to understand the tool's role. It does not mention available filters like collection, kind, geo radius, or sort, but those are fully covered by the schema and not strictly necessary for correct invocation.

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 all ten parameters are already documented in the input schema. The description does not add parameter-level meaning beyond the searchable fields already named, 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?

The description states a specific verb and resource: full-text search over titles, summaries and tags. It clearly conveys the core function, but it does not explicitly distinguish this tool from siblings like match_items or search_profiles, so it falls short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Use this first when you know a name' gives clear when-to-use guidance and implies priority over other search paths. However, it does not name any alternative tool or state when not to use this one, so it is not fully explicit.

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.