Skip to main content
Glama
flop-labs

technocore-mcp

by flop-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

write_note

Destructive

Write a durable note with optional conditional guards: create only if absent, or update only if value matches, preventing accidental overwrites.

Instructions

Write a durable note (<= 8192 characters). Optionally conditional: if_matches writes only when the note still holds that exact value, if_absent only when it does not exist yet. Send one condition, not both. A failed condition reports the value that is actually there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesNote key.
valueYesNote body, <= 8192 characters.
if_absentNoCreate-only guard.
namespaceYesNote namespace.
if_matchesNoCompare-and-set guard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.11.4
    • addedInput schema / properties / if_absent / default
      Added value: +false
    • addedInput schema / properties / if_absent / title
      Added value: +"If Absent"
    • addedInput schema / properties / if_matches / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / if_matches / default
      Added value: +null
    • addedInput schema / properties / if_matches / title
      Added value: +"If Matches"
    • removedInput schema / properties / if_matches / type
      Removed value: -"string"
    • addedInput schema / properties / key / description
      Added value: +"Note key."
    • addedInput schema / properties / key / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]{0,47}$"
    • addedInput schema / properties / key / title
      Added value: +"Key"
    • addedInput schema / properties / namespace / description
      Added value: +"Note namespace."
    • addedInput schema / properties / namespace / pattern
      Added value: +"^[a-z0-9][a-z0-9_-]{0,47}$"
    • addedInput schema / properties / namespace / title
      Added value: +"Namespace"
    • addedInput schema / properties / value / description
      Added value: +"Note body, <= 8192 characters."
    • addedInput schema / properties / value / title
      Added value: +"Value"
    • addedInput schema / title
      Added value: +"write_noteArguments"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Describes durability, conditional write behavior, and failure reporting of the actual value. Doesn't explicitly state that an unconditional write overwrites an existing note, but the destructiveHint annotation covers this.

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?

Two sentences that cover the essential behavior and conditions without unnecessary verbosity.

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?

Covers the main behavior and conditional outcomes, including failure reporting. Return value for success is not mentioned, but the description is otherwise adequate for a write tool.

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

Parameters5/5

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

Description adds meaningful semantics beyond the schema for the conditional parameters (if_matches and if_absent), explaining their exact behavior and relationship.

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?

Clear verb 'Write' and object 'durable note' with explicit constraints. Distinguishes from sibling read/list tools by being the write operation.

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?

Explains conditional writing with if_matches and if_absent, and instructs to send only one condition. Could be more explicit about when to use versus alternatives, but sibling names make this clear.

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

Deploy Server

Other Tools