Skip to main content
Glama

Upsert second-brain knowledge card

second_brain_upsert_card
Idempotent

Create or update a single structured knowledge card in 02_Knowledge, then update the vault index/log and make a focused git commit. It cannot delete, move, or write 01_Sources.

Instructions

Create or update one structured card in 02_Knowledge. It cannot delete, move, or write 01_Sources. After success, update the vault index/log as needed and make a focused git commit.

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": {
      "title": "<title>",
      "type": "<type>",
      "status": "<status>",
      "confidence": "<confidence>",
      "source": "<source>",
      "tags": "<tags>",
      "currentCognition": "<currentCognition>",
      "evidence": "<evidence>"
    },
    "name": "second_brain_upsert_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes
typeYes
titleYes
sourceYes
statusYes
evidenceYes
filenameNoOptional filename without .md; defaults to title.
confidenceYes
currentCognitionYes

Output Schema

NameRequiredDescriptionDefault
pathYes
createdYes
updatedYes
gitCommitRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the description's real contribution is the scope fence around 01_Sources and the post-success workflow (index/log update plus a git commit side effect). That is useful context an agent would not get from structured fields. However, the central behavior of an upsert with 8 required fields is unaddressed: it never says whether an existing card is fully replaced or merged, which is the single most consequential thing to know before calling it.

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 action, then the exclusion, then the follow-up obligations. No restatement of the title and no filler; every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the input side is badly under-covered: 8 required parameters with near-zero schema descriptions and no field guidance in the description. For a 9-parameter mutation tool, the omission of merge-versus-replace semantics and of any field meaning leaves real ambiguity about correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11% of 9 parameters, so the description is expected to compensate and does not: no parameter is named or explained. Nothing clarifies the enums (including the Chinese 高/中/低 confidence values), the meaning of currentCognition versus evidence, or the filename-over-title default beyond what the schema already says. An agent must read the raw schema for all field semantics.

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 gives a specific verb pair and resource: 'Create or update one structured card in 02_Knowledge.' That is far more informative than the title alone, and the location constraint ('02_Knowledge') scopes it against the broader vault. It stops short of naming a sibling such as second_brain_capture, so an agent must infer from names alone whether capture and upsert overlap.

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?

Implicit when-not guidance is present and concrete: it 'cannot delete, move, or write 01_Sources,' which tells the agent to look elsewhere for those operations. The third sentence also gives the required follow-up sequence (update index/log, make a focused git commit). It lacks an explicit comparison to sibling tools for the overlapping 'capture a new card' case.

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