Skip to main content
Glama

upsert_concept

Create or update a lasting Markdown note for a concept: a new name creates the note, while an existing name gets a dated update appended so nothing is duplicated or replaced.

Instructions

Keep one lasting note per concept in Claude/Concepts/. A new name creates the note; a name that already exists (letter case ignored) gets a dated update appended, so nothing is duplicated or replaced. Search before calling.

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": {
      "name": "<name>",
      "content": "<content>"
    },
    "name": "upsert_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the target location, case-insensitive name matching, and append-rather-than-replace semantics so nothing is duplicated. It omits concurrency behavior, authentication or path-creation requirements, and file format, which matter for a write tool.

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 short sentences, front-loaded with the core purpose, then the branching semantics, then the prerequisite action. No filler and nothing out of order.

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?

An output schema exists, so return values need no explanation, and for a two-parameter write tool the description covers destination, deduplication semantics, and the pre-check step. The remaining gap is the 'content' parameter's handling and the append format.

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 description coverage is 0%, so the description must compensate. It explains 'name' well (case-insensitive match, create-or-append decision) but says nothing explicit about 'content' beyond the vague implication that it is appended; the format of the dated update is also unspecified.

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 pair ('Keep one lasting note per concept in Claude/Concepts/') and immediately explains the two possible outcomes, so an agent knows exactly what invoking it produces. It stops short of naming a sibling tool, but the 'Search before calling' directive points at the search/query family.

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?

'Search before calling' is explicit pre-invocation guidance that steers the agent to a search tool first, which is the main routing decision here. It doesn't name the specific alternative or state when not to use this tool, so it falls short of a full when/when-not treatment.

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