Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

NicheDB: Search Items

nichedb_search_items
Read-onlyIdempotent

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

Served by NicheDB (https://nichedb.dev/docs/mcp).

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, e.g. elden ring
latNoQuery center latitude; requires long
bboxNowest,south,east,north; west > east crosses the antimeridian
kindNoItem kind, e.g. release, title, filing (optional)
longNoQuery center longitude; requires lat
sortNoResult order. distance (needs lat and long) puts the nearest first, e.g. "distance"; anything else keeps newest first
unitNoDefault km
limitNoRows to return, integer 1-100, default 20, e.g. 10
radiusNoDefault 10; maximum 1000 km
collectionNoCollection slug, e.g. games (see list_collections)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 and the description is not obliged to repeat it. The description adds the useful detail that matching is against titles, summaries and tags, but says nothing about result ordering defaults, pagination, or how geo constraints interact with the text query.

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?

The operative sentence comes first and there is no filler around it. The vendor attribution line is not needed for an agent to call the tool correctly, but it is short and does not obscure the core statement.

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?

This is a 10-parameter tool with geo radius/bbox/distance-sort behavior and no output schema, so the description is thin relative to its complexity. The schema compensates almost entirely, but an agent gets no description-level guidance on when geo filters are appropriate or what a result contains.

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 the parameter descriptions are unusually rich (bbox antimeridian note, distance-sort dependency, limit bounds, radius units), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the vague "when you know a name" framing, making 3 the appropriate baseline.

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" — and identifies the searched fields, which is more than the name alone conveys. It does not explicitly name the sibling it differs from (e.g. a semantic match tool), so differentiation is implied rather than stated.

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?

"Use this first when you know a name" gives a genuine usage cue tied to exact-ish lookup. However, it never names an alternative for the opposite case (searching by meaning rather than a name), and it says nothing about the geo/collection filtering path even though most of the schema is geo parameters.

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

All Profullstack toolsInspect
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.

Resources