Skip to main content
Glama

Configure Memory

by dev.configure.mcp
OverviewDiscussionsAdmin

configure_profile_commit

Close out a Configure-profile-backed turn by submitting bounded turn evidence and, optionally, durable memories worth keeping. Error -32009 (commit_required) from any configure tool is resolved ONLY by this call: commit, then retry the blocked call — never configure_connect, which is for sign-in. Call it at turn end even when you learned nothing durable: reads and searches created obligations regardless, and an empty commit with a one-line summary clears them. The runtime usually calls this for you after a profile read; call it yourself only when your host requires manual write-back. Prefer configure_profile_remember for a single fact the user explicitly stated; use commit to clear the obligation created by a configure_profile_read or configure_profile_search and to save memories drawn from the whole turn. Evidence is minimal: at most the specific user statements that support each memory, plus toolResults — never conversation history; memories are durable user facts, preferences, or intentions rather than provenance or assistant replies. Returns the obligations it cleared and any memories written (id, source, marker). Additive: it only records what this turn learned. It never deletes or overwrites existing memories, and never emails, posts, or publishes anything on the user's behalf.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
read_idNoOptional read id returned by a prior configure_profile_read or configure_profile_search obligation; pass it to tie this commit to that specific read.
memoriesNoOptional durable memory candidates to save, one clear fact per entry. Only include durable user facts, preferences, or intentions; do not summarize provenance, the conversation, or assistant replies.
messagesNoOptional minimal evidence to clear read-backed commit obligations: at most the one or two user statements that directly support each saved memory. Never send conversation history or any messages beyond those supporting statements.
toolResultsNoOptional bounded tool result evidence, each with toolName and content, used as evidence to clear read-backed commit obligations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
memoriesNo
committedNo
obligationsNoRead obligations this commit cleared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: additive-only semantics, never deletes or overwrites, never emails/posts/publishes, and describes the return payload (obligations cleared, memories written with id/source/marker). These traits are consistent with destructiveHint=false and readOnlyHint=false.

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 the core purpose and error-resolution rule, and most sentences earn their place, but the evidence-minimality rule is stated twice (once in prose, once per-parameter) and the parameter guidance slightly duplicates the schema.

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

Completeness5/5

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

An output schema exists, so return values need not be detailed, yet the description still summarizes them. It covers obligations, the error path, evidence bounds, and additive semantics — everything needed to invoke correctly.

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 coverage is 100%, so baseline is 3, but the description reinforces the constraints on each parameter: read_id ties the commit to a specific read obligation, memories must be durable facts not provenance, and evidence is limited to supporting user statements plus toolResults.

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 and resource ('Close out a Configure-profile-backed turn by submitting bounded turn evidence and, optionally, durable memories') and distinguishes itself from siblings by naming configure_connect and configure_profile_remember with the conditions that select each.

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?

Explicitly covers when to call (turn end, even with nothing learned, because reads/searches create obligations), when not to (only when the host requires manual write-back; the runtime usually handles it), the -32009 resolution path, and the alternative (configure_profile_remember for a single stated fact).

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

All Configure Memory 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