Skip to main content
Glama
Sign In

MindThread

by io.github.ppcvote
OverviewDiscussionsAdmin

Save a brand document

save_brand_doc
DestructiveIdempotent

Saves a brand, content or content-map document (Markdown or plain text, up to 50,000 characters) under a doc_id such as brand, content or content_map, as a new version; the last 20 versions are kept. Pass base_version (the version you read, 0 when creating) so a concurrent edit is refused instead of overwritten. Nothing is published. Applies after interviewing the user about their brand, summarizing their top posts, or drafting a content map. 繁中：存品牌文件、內容文件或內容地圖，保留最近 20 版。

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

Input Schema

NameRequiredDescriptionDefault
titleNoUp to 100 characters
doc_idYes1-40 chars of a-z, 0-9, _ or -; suggested: brand, content, content_map
contentYesWhole document, Markdown or plain text, up to 50,000 characters
languageNoBCP 47 tag, e.g. zh-TW (default), en, ja
account_idNoOptional connected account the document belongs to
base_versionNoVersion you read; 0 when creating

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing version retention (last 20 kept), the optimistic-concurrency contract via base_version where a stale write is refused rather than overwriting, and that nothing is published. The 'nothing is published' note is especially valuable given destructiveHint=true, since it clarifies the blast radius is limited to the stored document.

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 action and length limit, then versioning, then concurrency, then usage triggers — a sensible priority order. It is a long semicolon-chained sentence that repeats the 50,000-character limit already in the schema, and the appended Chinese line adds length for non-zh readers.

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 6-parameter mutation with no output schema and full schema coverage, it covers storage semantics, retention, concurrency, and side effects. The one missing piece is what the call returns (presumably the new version number needed for subsequent base_version values), which matters for chained edits.

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% and already documents each field, so the baseline is 3. The description still adds meaning by explaining the purpose of base_version (concurrency guard against overwriting) rather than just restating '0 when creating', which is the parameter most likely to be misused.

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 (Saves) and resource (brand/content/content-map document) plus the storage key (doc_id), and makes the versioning model explicit ('as a new version'). An agent can immediately tell this apart from the read-side sibling get_brand_doc 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?

Gives concrete triggering contexts: after interviewing the user about their brand, summarizing top posts, or drafting a content map. It does not state exclusions (e.g., use update_library_item instead for individual posts, or that reading should go through get_brand_doc), so it is clear on when to use but silent on when not to.

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

All MindThread toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources