Skip to main content
Glama
Sign In

NicheDB

by dev.nichedb
OverviewDiscussionsAdmin

add_source

Add a source: an adapter with a config, fetched on a schedule (needs a key; admins and Pro). Call list_adapters first for the fields.

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": {
      "adapter": "<adapter>"
    },
    "name": "add_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name, e.g. Bun releases
configNoAdapter config fields from list_adapters, e.g. {"repo": "oven-sh/bun"}
adapterYesAdapter name from list_adapters, e.g. github-releases
collectionNoCollection slug, e.g. packages; defaults to the adapter's
cadence_minutesNoMinutes between fetches, integer 5-1440, e.g. 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / adapter / description
      Previous value: -"Adapter name, e.g. github-releases"New value: +"Adapter name from list_adapters, e.g. github-releases"
    • changedInput schema / properties / cadence_minutes / description
      Previous value: -"5 to 1440"New value: +"Minutes between fetches, integer 5-1440, e.g. 60"
    • changedInput schema / properties / collection / description
      Previous value: -"Collection slug; defaults to the adapter's"New value: +"Collection slug, e.g. packages; defaults to the adapter's"
    • changedInput schema / properties / config / description
      Previous value: -"Adapter config fields"New value: +"Adapter config fields from list_adapters, e.g. {\"repo\": \"oven-sh/bun\"}"
    • changedInput schema / properties / name / description
      Previous value: -"Display name"New value: +"Display name, e.g. Bun releases"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, open-world, non-idempotent, non-destructive write. The description adds real value beyond that: the authorization requirement (key, admin, Pro tier) and the dependency on list_adapters. It omits what happens on a duplicate source or whether a fetch fires immediately after creation, so it is strong but not exhaustive.

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?

A single sentence with a parenthetical, front-loaded with the action and resource before the prerequisite and the auth caveat. No filler, and every clause 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?

For a 5-parameter mutation with a nested config object and no output schema, the description covers the hardest part: where valid adapter/config fields come from. Auth and tier gating are also present. What it lacks is any hint of the post-creation behavior or return value, which matters somewhat given there is no output schema.

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 coverage is 100% and the parameter descriptions already state that 'adapter' and 'config' values come from list_adapters, with examples and cadence bounds (5-1440). The description's 'call list_adapters first' restates that same guidance rather than adding new semantics, so the baseline 3 is appropriate.

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 ('Add') and resource ('source'), then defines the resource inline as 'an adapter with a config, fetched on a schedule', which disambiguates it from siblings like list_sources, run_source, and list_adapters. An agent can tell what is being created without opening the 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?

'Call list_adapters first for the fields' is an explicit prerequisite that routes the agent to the right sibling before invoking. It also names the gating conditions ('needs a key; admins and Pro'). It stops short of naming alternatives or exclusions (e.g., when to use run_source vs. this), so it is clear context but not a full when/when-not map.

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