Skip to main content
Glama

NicheDB

by dev.nichedb
OverviewDiscussionsAdmin

update_profile

Edit a profile you own (needs a key). Send markdown, a whole OpenProfile.md that replaces what you wrote before, or any of name, headline, emoji, pronouns, web, identity (key: value, null removes), sections (name: body, none removes), handle, public. What you write wins over every source and survives every re-read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesProfile id, slug-id or handle
webNoYour home page (Website, Homepage and Site are the same key); empty removes
nameNoThe name
emojiNoYour mark next to your name: one emoji or an OpenEmoji :shortcode:; empty removes
handleNoYour URL: /c/profiles/<handle>
publicNoListed and pulled by other directories
headlineNoOne line
identityNoIdentity keys: Kind, Emoji, Pronouns, Web, Email, Location, ...; null removes
markdownNoA complete OpenProfile.md
pronounsNoAs you write them (she/her, they/them, any); empty removes, never inferred
sectionsNoSection bodies by name (accounts, topics, broadcast, guest, ...); the word none removes one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / emoji
      Added value: +{
+  "description": "Your mark next to your name: one emoji or an OpenEmoji :shortcode:; empty removes",
+  "type": "string"
+}
    • changedInput schema / properties / identity / description
      Previous value: -"Identity keys: Kind, Web, Email, Location, ...; null removes"New value: +"Identity keys: Kind, Emoji, Pronouns, Web, Email, Location, ...; null removes"
    • addedInput schema / properties / pronouns
      Added value: +{
+  "description": "As you write them (she/her, they/them, any); empty removes, never inferred",
+  "type": "string"
+}
    • addedInput schema / properties / web
      Added value: +{
+  "description": "Your home page (Website, Homepage and Site are the same key); empty removes",
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the auth requirement ('needs a key'), destruction semantics ('replaces what you wrote before', 'null removes', 'none removes'), and precedence ('wins over every source and survives every re-read'). It omits response/error behavior, which keeps it short of a 5.

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?

Front-loads the action and precondition, then packs the parameter semantics into one dense sentence. The parameter enumeration is list-heavy but every item carries a removal rule or format note, so it earns its space.

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 an 11-parameter mutation tool with nested objects and no annotations, the description covers auth, destruction, and precedence well; no output schema means return values need not be explained. It lacks any error/failure guidance, which is the main remaining gap.

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 genuine semantics the schema lacks: that `markdown` is a whole-document replacement versus the field-level merge path, and the null/none removal conventions. That merge-vs-replace distinction is the key thing an agent needs and isn't stated in the schema.

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 ('Edit a profile you own') and adds an ownership precondition that separates it from sibling claim_profile. An agent can distinguish it from get_profile and search_profiles without opening any schema.

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?

The '(needs a key)' note gives an implicit auth/ownership prerequisite, which is useful usage context, but the description never names an alternative tool or states when not to use this one. Usage is implied rather than spelled out.

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