Skip to main content
Glama

Change a concept's details

set_concept
Destructive

Change anything about a concept except its content: its name, its when_to_read (the moment it should be opened), other names it can be found by, and the tags it carries. Concepts tagged boot are loaded by login at the start of every conversation. Removing a name or a tag keeps the concept.

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": {
      "concept": "<concept>"
    },
    "name": "set_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new name.
conceptYesThe concept's name, one of its other names, or its ID.
add_tagsNoTags to add it to.
add_aliasesNoOther names to add.
remove_tagsNoTags to take it out of.
when_to_readNoThe moment this concept will be needed.
remove_aliasesNoOther names to remove.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=false, and the description adds two genuinely behavioral facts the annotations cannot convey: 'Removing a name or a tag keeps the concept' scopes what destruction actually means, and the note that concepts tagged boot are loaded by login at the start of every conversation warns of a global side effect of add_tags. That is real context beyond the structured fields.

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 tight sentences with the scope constraint front-loaded and zero filler. Minor friction from 'Removing a name or a tag', since the schema only offers remove_aliases/remove_tags and no remove_name, which could momentarily confuse an agent.

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?

With 7 parameters, one required, no output schema, and a destructive mutation, the description covers what is editable, what is not, and the key side effect of the boot tag. It does not say whether omitted fields are left untouched or what happens to references on rename, which are small residual gaps.

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 glosses the non-obvious parameters: when_to_read as 'the moment it should be opened', aliases as 'other names it can be found by', and tags including the special boot semantics. It adds meaning about consequences rather than just restating definitions.

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 ('Change anything about a concept') and then enumerates the exact editable fields: name, when_to_read, other names, tags. It explicitly bounds scope against the sibling update_content by saying 'except its content', so an agent can tell the two apart without opening either 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?

The phrase 'except its content' steers content edits elsewhere (update_content), and the description makes clear this tool is for metadata only. It gives clear context but never names the alternative tool or states a hard exclusion rule, so it stops short of a 5.

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