Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

feedback_save

Save a behavioral rule, preference, or correction that should guide future agent behavior. Use this when the user gives explicit guidance like 'always reply in Russian', 'don't suggest meetings before 11am', or 'invoice link goes via email, not chat'. Structure the rule as: the rule itself, why it matters (if stated), and how to apply it. Scope: 'workspace' for org-wide rules, 'agent' for per-agent overrides, 'person' for per-contact preferences. Prefer feedback.save over notes.save for anything that's instructive rather than informational.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesShort identifier for this rule (e.g. 'reply_language', 'meeting_hours'). Must not start with '__' (reserved).
whyNoWhy this rule matters (optional but recommended for the distiller).
ruleYesThe rule itself, in imperative form. Required.
scopeYesScope of the rule. 'workspace' for org-wide rules; 'agent' for per-agent overrides; 'thread' for conversation-specific guidance; 'person' for per-contact preferences. 'global' accepted as deprecation alias for 'agent'.
how_to_applyNoWhen/how to apply the rule (optional). Helpful for conditional rules like 'apply when speaking to Russian-speaking customers'.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
scope_ref_idNoRequired for scope='thread' (thread_id) and scope='person' (person_id).
target_agent_idNoTarget agent. In agent mode optional (defaults to self); required from MCP. Ignored when scope='workspace'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the write/safety profile (readOnlyHint=false, destructiveHint=false), so the bar is lower. The description adds that saved rules persist and "guide future agent behavior," which clarifies the lasting side effect beyond the annotations. It does not address the non-idempotent hint (what happens on repeated saves), so it is not fully complete but adds real value.

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?

Purpose is front-loaded, followed by usage examples, structuring advice, scope, and sibling preference in a sensible order. Every sentence is useful, though the scope sentence partially duplicates the schema enum descriptions, adding mild redundancy.

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?

No output schema exists, yet the description covers purpose, trigger conditions, structuring, and scoping, which is most of what an agent needs. It omits any note on the non-idempotent behavior and the in_workspace/target_agent_id semantics, though those are documented in the schema itself.

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 description coverage is 100%, so the baseline is 3. The description adds structural guidance ("the rule itself, why it matters, and how to apply it") that maps to the rule/why/how_to_apply parameters, going beyond the schema's field-level text. However, the scope explanation largely restates the enum's own descriptions, limiting the added value.

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 ("Save") and resource ("behavioral rule, preference, or correction") with concrete examples, and explicitly contrasts with the sibling notes.save. An agent can tell exactly what this does and how it differs from alternatives without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ("when the user gives explicit guidance like 'always reply in Russian'") and names the alternative with a selecting condition ("Prefer feedback.save over notes.save for anything that's instructive rather than informational"). Both when-to-use and when-to-use-something-else are covered.

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

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