Skip to main content
Glama

Hyreflow

hyreflow_knowledge_write

Destructive

Create or change one note in this workspace's second brain. With an existing slug only the fields given change, and its sources stay. Without one, title is required and the slug comes from it, and a slug already taken is refused rather than replaced. status archived takes a note out of search. Every member's agent reads the change at once and there is no undo, so a note is saved only when the user asked for it or said yes to its exact text, and a note the build wrote is changed only when the user asks. A note holds facts about the agency and its clients, not about a named person. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hyreflow_knowledge_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown, [[links]] allowed
slugNo
tagsNo
titleNo
folderNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely new consequences: changes are immediately visible to every member's agent, there is no undo, and a taken slug is refused rather than silently overwriting an existing note. It also discloses the archived-status side effect (removed from search) and notes the tool is free.

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?

Front-loaded with the core verb and the create-vs-update rule, followed by consequences and policy, so the most decision-relevant facts come first. The final policy sentence is long and comma-chained, and the trailing "Free." is marginally useful but sits oddly outside the flow.

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 destructive, no-output-schema mutation with six parameters, the description covers the risk profile, conflict behavior, cross-member visibility, and permission-ish gating well. Gaps remain around return values (does it return the resulting slug?), tag/folder semantics, and title-change behavior on an existing note.

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 coverage is only 17% (only `body` is documented), so the description must carry weight, and it does explain the `slug`/`title` dependency and the meaning of `status: archived`. However, `tags` and `folder` get no explanation at all, and it never says what happens to the slug if `title` changes on an existing note.

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?

"Create or change one note in this workspace's second brain" gives a specific verb pair plus a precisely scoped resource, and the create-vs-update split is spelled out via `slug` presence. An agent can distinguish this from hyreflow_knowledge_read / _search / _import purely from the text, since it is the only one framed as an upsert of a single note.

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 description gives unusually concrete when-to-use conditions: save only when the user asked for it or approved its exact text, and change a build-written note only when the user asks. It also bounds content scope (agency/client facts, not named individuals). It stops short of naming sibling alternatives such as hyreflow_knowledge_import for bulk loading, so it is strong context but not a full routing rule.

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.