Skip to main content
Glama
Sign In

NicheDB

by dev.nichedb
OverviewDiscussionsAdmin

search_profiles

Read-onlyIdempotent

People: one entry per person assembled from every app that serves their OpenProfile.md (podcasters from p0dcasters, public profiles from OutreachGraph). Search by name, headline or anything in the document; newest change first. Each answer carries the page, the openprofile.md URL, accounts, topics, Broadcast shows, the Guest section, and the job title, company and seniority the person published (filter on them with title, company, seniority or tags).

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

Input Schema

NameRequiredDescriptionDefault
qNoText to match against the name, headline and document (optional)
tagsNoFacet tags every result must carry: title:…, company:…, seniority:…
limitNoRows to return, integer 1-200, default 30, e.g. 50
sinceNoISO 8601 time: only profiles changed after it (optional), e.g. 2026-10-01T00:00:00Z
titleNoJob title, matched as its tag (`CTO` is title:cto) (optional)
companyNoCompany domain, URL or name (optional), e.g. example.com
seniorityNoSeniority derived from the title (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Company domain, URL or name (optional)"New value: +"Company domain, URL or name (optional), e.g. example.com"
    • 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 / since / description
      Previous value: -"ISO time: only profiles changed after it (optional)"New value: +"ISO 8601 time: only profiles changed after it (optional), e.g. 2026-10-01T00:00:00Z"
  2. Changed4 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
+  "description": "Company domain, URL or name (optional)",
+  "type": "string"
+}
    • addedInput schema / properties / seniority
      Added value: +{
+  "description": "Seniority derived from the title (optional)",
+  "enum": [
+    "c-suite",
+    "vp",
+    "director",
+    "manager",
+    "senior",
+    "entry"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Facet tags every result must carry: title:…, company:…, seniority:…",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "description": "Job title, matched as its tag (`CTO` is title:cto) (optional)",
+  "type": "string"
+}
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the description only needs to add context. It does: results are merged across multiple source apps, ordered by newest change, and each row carries page, openprofile.md URL, accounts, topics, Broadcast shows, Guest section and published role data. It does not discuss result caps or how pagination works beyond the schema's limit.

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 sentences, front-loaded with the resource definition before the capability and the return inventory. The long parenthetical-style enumeration of returned fields is dense and full of internal jargon (p0dcasters, OutreachGraph) but each item carries information an agent needs.

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 no output schema, the description correctly takes on the burden of describing the return shape, and all seven parameters are covered by the schema. It leaves minor gaps around result capping/paging when limit is hit and how multiple filters are combined, which matters for a 7-param search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by linking the returned fields to the filter parameters ('filter on them with title, company, seniority or tags') and revealing the facet tag syntax (title:…, company:…, seniority:…) that the tags array expects. It does not clarify interaction between q and tags or how 'since' combines with ordering.

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

Purpose5/5

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

States a specific verb and resource ('People: one entry per person') and explains what the entries are assembled from (OpenProfile.md sources like p0dcasters and OutreachGraph). An agent can distinguish this discovery search from get_profile and find_profile_by_linkedin without opening a schema.

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?

Gives clear search semantics ('by name, headline or anything in the document; newest change first') and tells the agent which filters to apply for title/company/seniority/tags. It never explicitly names when to prefer a sibling like find_profile_by_linkedin (known LinkedIn URL) or get_profile (known identity), so the alternative-routing is only implied.

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

All NicheDB 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