Skip to main content
Glama

Niche of One Network

Set my interests

set_interests
DestructiveIdempotent

Members. Save the topics you want your personal brief built from (replaces the saved list; an empty list clears it). Shows what it will save first; call again with confirm true.

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": {
      "interests": "<interests>"
    },
    "name": "set_interests"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave out to preview; true to commit.
interestsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description supplies the specific consequence that annotations cannot: the saved list is replaced wholesale and an empty list wipes it. It also discloses the preview-before-commit behavior, which is the key safeguard for a destructive write. Return format and error behavior are left unstated.

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?

Three tight clauses in a single sentence, front-loaded with the resource, then the destructive semantic, then the confirm workflow. Nothing is padded or repeated from structured fields.

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 two-parameter destructive mutation with no output schema, the definition covers the essential risks: what gets replaced, how to clear, and how to preview safely. It does not describe what the preview actually shows, but the agent has enough to call it correctly.

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 50% — confirm is documented in-schema but interests is not. The description compensates by explaining that the interests list replaces prior state and that an empty list clears it, and it restates confirm's preview/commit meaning. Length and count limits remain only in the schema, which is acceptable.

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?

The description names a specific verb and resource — save topics that the personal brief is built from — and adds the replacement scope (an empty list clears it). That is enough to distinguish it from read-only siblings like my_brief. It stops short of naming an explicit sibling to prefer instead, which keeps it off a 5.

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?

It gives a clear two-step usage pattern: call without confirm to preview, call again with confirm true to commit. The 'Members.' lead-in signals an audience/access precondition. What is missing is any statement of when to use this versus inspecting interests elsewhere, so there is context but no explicit alternatives or exclusions.

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