Skip to main content
Glama

Propose Profile Mutation

propose_profile_mutation

Propose a change to one profile field for later review; the active profile is never changed.

Stores value as a new memory in the proposals bucket at path 'profile.{field}' with metadata status 'proposed'.

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": {
      "field": "<field>",
      "value": "<value>"
    },
    "name": "propose_profile_mutation"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesProfile field name; the proposal is stored at path profile.<field>.
scopeNoOptional scope that narrows memory access; leave blank for the token default.
valueYesProposed new value, stored as the proposal's content.
team_idNoOptional team/workspace identifier for team-scoped memory access.
agent_idNoOptional client-supplied agent label for memory attribution.
metadata_jsonNoOptional JSON object of extra metadata; status, proposed_by_agent_id, proposal_type and profile_field are set by the server.{}
agent_instance_idNoOptional stable, non-secret agent instance ID for per-client attribution.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / properties / agent_id / title
      Removed value: -"Agent Id"
    • removedInput schema / properties / agent_instance_id / title
      Removed value: -"Agent Instance Id"
    • changedInput schema / properties / field / description
      Previous value: -"Input value for the Propose Profile Mutation tool."New value: +"Profile field name; the proposal is stored at path profile.<field>."
    • removedInput schema / properties / field / title
      Removed value: -"Field"
    • changedInput schema / properties / metadata_json / description
      Previous value: -"Optional JSON object string with extra metadata for the operation."New value: +"Optional JSON object of extra metadata; status, proposed_by_agent_id, proposal_type and profile_field are set by the server."
    • removedInput schema / properties / metadata_json / title
      Removed value: -"Metadata Json"
    • removedInput schema / properties / scope / title
      Removed value: -"Scope"
    • removedInput schema / properties / team_id / title
      Removed value: -"Team Id"
    • changedInput schema / properties / value / description
      Previous value: -"Input value for the Propose Profile Mutation tool."New value: +"Proposed new value, stored as the proposal's content."
    • removedInput schema / properties / value / title
      Removed value: -"Value"
    • removedInput schema / title
      Removed value: -"propose_profile_mutationArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"propose_profile_mutationOutput"
  2. Added
  3. Removed
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior. The description adds genuinely new context: the change is written into the proposals bucket at a deterministic path 'profile.{field}' with metadata status 'proposed', which explains the persistence side effect and why repeat calls create distinct entries. It does not mention permission requirements or how proposals are later reviewed.

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?

Two short sentences, with the key guarantee ('the active profile is never changed') front-loaded directly after the purpose. Nothing is redundant or padded, and the storage detail is separated into its own sentence.

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?

With 7 parameters fully documented in the schema, an output schema present, and annotations covering the safety profile, the description only needs to explain the non-obvious proposal semantics, which it does. The main residual gap is that it does not state that repeated proposals are not deduplicated (non-idempotent), leaving an agent to infer that from annotations.

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 scope, team_id, agent_id and metadata_json is already documented. The description only restates the storage-path convention for 'field', which the schema already states, so it adds little meaning beyond the structured fields. Baseline 3 applies.

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 verb and resource (propose a change to one profile field) plus its scope ('one profile field'). It clearly distinguishes itself from a real mutation by stating the active profile is never changed. It does not name the sibling proposal tools (propose_write, propose_todo_mutation), but the 'profile field' qualifier makes the target unambiguous.

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 phrase 'for later review' implies the intended workflow (staging a change for approval rather than applying it), and 'the active profile is never changed' tells the agent when this tool is appropriate. However, there is no explicit comparison to alternatives such as propose_write or update_memory, so the agent must infer when this is preferred over a direct mutation.

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.