Skip to main content
Glama
Sign In
agent-reasoning-mcp

agent-reasoning-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_utility_weights

Configure, inspect, activate, or nudge multi-attribute utility weight profiles to define AI decision preferences such as aggression, caution, greed, and exploration.

Instructions

Configure, inspect, activate, or incrementally nudge multi-attribute utility weight profiles (actions: configure, get, list, activate, nudge). Use set_utility_weights instead of evaluate_situation when defining decision preferences (aggression, caution, greed, exploration) rather than evaluating actions.

Returns configured utility profile, active weight map, or profile directory.

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": {
      "action": "<action>"
    },
    "name": "set_utility_weights"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoProfile name (e.g. "aggressive", "cautious", "explorer")
deltaNoKey-value map of weight deltas for nudge action
actionYesProfile operation: configure, get, list, activate, nudge
projectNoTarget project slug
weightsNoKey-value map of weight values (0.0 to 1.0)
is_activeNoWhether to set as currently active profile
descriptionNoProfile description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / action / description
      Previous value: -"Profile operation: configure, get, list, activate"New value: +"Profile operation: configure, get, list, activate, nudge"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "configure",
-  "get",
-  "list",
-  "activate"
-]New value: +[
+  "configure",
+  "get",
+  "list",
+  "activate",
+  "nudge"
+]
    • addedInput schema / properties / delta
      Added value: +{
+  "description": "Key-value map of weight deltas for nudge action",
+  "type": "object"
+}
  2. Changed2 schema fields changedv0.3.1
    • changedInput schema / properties / action / description
      Previous value: -"Profile operation"New value: +"Profile operation: configure, get, list, activate"
    • addedInput schema / properties / action / enum
      Added value: +[
+  "configure",
+  "get",
+  "list",
+  "activate"
+]
  3. Changed11 schema fields changedv0.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / action / description
      Added value: +"Profile operation"
    • removedInput schema / properties / action / enum
      Removed value: -[
-  "configure",
-  "get",
-  "list",
-  "activate"
-]
    • addedInput schema / properties / description / description
      Added value: +"Profile description"
    • addedInput schema / properties / is_active / description
      Added value: +"Whether to set as currently active profile"
    • addedInput schema / properties / name / description
      Added value: +"Profile name (e.g. \"aggressive\", \"cautious\", \"explorer\")"
    • addedInput schema / properties / project / description
      Added value: +"Target project slug"
    • removedInput schema / properties / weights / additionalProperties
      Removed value: -true
    • addedInput schema / properties / weights / description
      Added value: +"Key-value map of weight values (0.0 to 1.0)"
    • removedInput schema / properties / weights / properties
      Removed value: -{}
  4. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds the return surface (configured profile, active weight map, or profile directory), which is genuinely useful given no output schema exists, but says nothing about side effects of activate/nudge or auth requirements. Adequate, not rich.

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 purpose and action list, then the routing rule, then returns — a sensible ordering with no filler sentences. The action list is restated from the enum, a minor redundancy that keeps it from a 5.

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 7-parameter multi-action tool with nested objects and no output schema, the definition covers purpose, action routing, alternative selection, and the shape of returns. It is close to complete; the only gap is per-action behavioral detail for the mutating actions.

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 description coverage is 100%, so every parameter including the action enum is already documented in the schema; baseline 3 applies. The description adds no syntax, range, or interaction detail (e.g. how delta composes with weights) beyond what the schema states.

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 resource (multi-attribute utility weight profiles) with an explicit verb set and enumerates the five supported actions, so the agent knows exactly what operations this tool performs. It also names the sibling it must not be confused with (evaluate_situation) and the distinction between them, which is more than most definitions provide.

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?

Explicitly gives the selection rule: use this instead of evaluate_situation when defining decision preferences rather than evaluating actions. That is a clear when-to-use-vs-alternative statement. It does not, however, give per-action guidance (e.g. when to nudge vs configure), which keeps it short of a full 5.

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