Skip to main content
Glama
Sign In

WhyVault

by io.whyvault
OverviewDiscussionsAdmin

Update section

update_section
DestructiveIdempotent

Replace the content under one heading (up to the next heading of the same or higher level). The heading line itself stays. If the heading exists several times, you get the candidates and must be more specific.

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": {
      "path": "<path>",
      "heading": "<heading>",
      "content": "<content>",
      "change_summary": "<change_summary>"
    },
    "name": "update_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
contentYesNew Markdown for the section body.
headingYese.g. „Status“, „## Status“ or „Projekt > Status“.
change_summaryYesOne short line for the user's history, e.g. „Protokoll vom Kundentermin ergänzt“.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real substance on top: exactly what is destroyed (body under the heading only), what survives (the heading line), and the duplicate-heading candidate flow. It stops short of stating what happens on a missing heading or whether empty content deletes the body entirely.

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 tight sentences, zero filler, with the scoping rule and the preserved-heading caveat front-loaded before the edge case. Every sentence carries distinct information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers the core write semantics and one failure mode, but leaves the missing-heading behavior, permission requirements, and the purpose of change_summary unexplained. Adequate but with clear gaps an agent would hit in practice.

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 75%, so heading, content and change_summary already carry descriptions; the description only adds the duplicate-heading matching semantics, which is genuinely useful for the 'heading' parameter. Nothing is added for 'path' or for how heading matching treats level prefixes beyond what the schema example shows.

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?

States a specific verb and resource ("Replace the content under one heading") plus a precise scope boundary ("up to the next heading of the same or higher level") and notes the heading line is preserved. The section-level scope implicitly separates it from replace_note and append_to_note, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful conditional guidance for the ambiguous case (duplicate headings return candidates and require a more specific heading), which tells the agent how to recover. It never says when to choose this over append_to_note or replace_note, and does not cover the case where the heading does not exist.

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

All WhyVault 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