Skip to main content
Glama

Saved User Strategy State

strategy
Destructive

Store user-authored strategy text, execution timestamps, and the most recent result in encrypted per-user storage. This tool does not provide presets, define opportunities, choose domains, or execute a workflow. Requires a registered account with memory enabled.

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": "strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSaved strategy ID for update or delete.
nameNoOptional user-defined name for set.
actionNoget, set, update, or delete. Defaults to get.
resultNoLatest user- or host-supplied result summary for update.
strategyNoUser-authored text, maximum 500 characters, for set.

Output Schema

NameRequiredDescriptionDefault
maxNo
errorNo
totalNo
messageNo
successNo
strategyNo
strategiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Beyond the annotations, the description adds useful context: encrypted per-user storage and a registered-account-with-memory requirement. It also clarifies that the tool does not execute workflows or provide presets, which supports the openWorldHint=false annotation. But given destructiveHint=true and a delete action, it does not disclose what deletion removes or whether it is reversible.

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?

The description is front-loaded with the core storage purpose and then adds boundary conditions and prerequisites in compact sentences. The exclusions are useful for scope-setting, though the negative list could be tightened slightly. Overall it is appropriately sized and has little waste.

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?

Given the 5-parameter schema with full descriptions, an output schema, and rich annotations, the description covers the key external context: encryption, per-user scope, account prerequisite, and non-capabilities. It is not fully complete because it omits action-level guidance and deletion semantics, but those gaps are partly filled by the schema and destructive hint.

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 the parameter meanings are already well documented in the input schema. The description adds general context about storing strategy text and results but does not add syntax, action-specific semantics, or constraints beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific resource and operation: storing user-authored strategy text, execution timestamps, and the latest result in encrypted per-user storage. It also explicitly excludes several adjacent capabilities, helping distinguish it from sibling domain tools. The main gap is that the verb 'Store' underplays the get/update/delete actions exposed by 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 Guidelines3/5

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

The description implies when this tool applies by saying it does not provide presets, define opportunities, choose domains, or execute workflows, and it adds a prerequisite of a registered account with memory enabled. However, it does not explicitly say when to prefer this tool over an alternative, nor does it explain when to choose get versus set versus update versus delete.

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.