Skip to main content
Glama

Set what their videos are about

set_niche

Saves the member's niche. One of: business (Business and marketing), ai-tech (AI and tech), coaching (Coaching and personal growth), health (Health and wellness), fitness (Fitness), beauty-fashion (Beauty and fashion), food (Food and cooking), parenting (Parenting and family), money (Money and finance), travel-lifestyle (Travel and lifestyle), education (Education and how-to), entertainment (Comedy and entertainment), other (Something else).

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": {
      "niche": "<niche>"
    },
    "name": "set_niche"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says "Saves" but not whether this overwrites an existing niche, whether prior values are preserved, what permissions or member context are required, or what the call returns.

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 core action is front-loaded in the first four words, followed by the necessary enumeration. Every element earns its place, though the value list is dense and could be formatted more scannably.

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?

With one required parameter and no output schema, the parameter side is well covered, but the description omits mutation semantics (overwrite behavior, idempotency) and any hint of when the call is appropriate. That leaves real gaps for a tool with no annotations to lean on.

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 description coverage is 0%, but the description fully compensates for the single parameter by giving a human-readable gloss for every enum value. This is genuinely useful for disambiguation — for example, separating health from fitness, or business from money — which the raw slugs alone would not resolve.

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?

"Saves the member's niche" states a specific verb and resource, and the inline enumeration makes the scope of the write unambiguous. It does not explicitly distinguish itself from siblings such as get_profile or remember, but the action is clear enough to select 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this — e.g., during onboarding, only when the member corrects their niche, or whether it can be called repeatedly. No alternatives or exclusions are named, leaving the agent to infer timing entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources