Skip to main content
Glama
Sign In

NicheDB

by dev.nichedb
OverviewDiscussionsAdmin

claim_profile

Idempotent

Claim a profile as the key owner (needs a key). Proven when the key owner’s email is one the profile lists, or when the person’s site or show page links back to the profile’s nichedb page. An admin may claim on behalf of an email.

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": {
      "ref": "<ref>"
    },
    "name": "claim_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesProfile id, slug-id or handle, e.g. 4821, ada-lovelace-4821 or ada
emailNoAdmins only: claim it for this email address, e.g. ada@example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Admins only: claim it for this email"New value: +"Admins only: claim it for this email address, e.g. ada@example.com"
    • changedInput schema / properties / ref / description
      Previous value: -"Profile id, slug-id or handle"New value: +"Profile id, slug-id or handle, e.g. 4821, ada-lovelace-4821 or ada"
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, non-destructive), so the lower bar applies. The description adds real value beyond that: how ownership is proven (email match or a backlink from the person's site/show page) and that an admin may claim on behalf of an email. It does not cover what happens if proof fails or what the existing claim state becomes.

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?

Three sentences, front-loaded with the core action and prerequisite, then the proof mechanics, then the admin path. Every sentence carries load, though the parenthetical "(needs a key)" is slightly terse relative to the verification detail that follows.

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 state-changing, non-idempotent-looking claim operation with no output schema, the description explains how a claim qualifies but not what the call returns, what happens on verification failure, or what occurs to a pre-existing owner. These are material gaps for a mutation tool, though the core mechanics are well covered.

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%, so both parameters are already documented, and the baseline of 3 applies. The description reinforces that 'email' is an admin-only affordance but adds no syntax or edge-case detail (e.g., what ref formats are accepted, precedence when both ref and email are supplied).

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 verb+resource ('Claim a profile as the key owner'), which clearly distinguishes it from siblings like get_profile or update_profile. It does not explicitly name a sibling to differentiate against, but the ownership/claim framing is unambiguous.

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?

Adds prerequisites ("needs a key") and an admin path, which implies context for use. However, it does not say when to prefer claim_profile over siblings such as update_profile or search_profiles, leaving the selection to inference.

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