Skip to main content
Glama

Setup Memory

setup_memory
Read-onlyIdempotent

Derive project_key from a git remote and return an idempotent rule block for local agent config files. Does not write to the filesystem.

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

Input Schema

NameRequiredDescriptionDefault
repo_pathNoLocal repo path hash fallback
user_slugNoUser-picked project slug
git_remoteNoGit remote URL for project_key derivation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

'Does not write to the filesystem' largely restates readOnlyHint=true and destructiveHint=false, and 'idempotent' repeats idempotentHint=true, so it earns limited credit beyond structured fields. It does add one piece of real value by revealing that the output is a rule block intended for the caller to place in config files, which clarifies the read-only contract operationally.

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 derivation purpose and returned artifact front-loaded and the non-writing guarantee as a single trailing clause. Nothing is redundant or padded.

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 three-optional-parameter, no-output-schema tool, the description covers the input source, the returned artifact, and the absence of side effects. It leaves open what happens when no remote is available and how fallbacks are prioritized, but that is minor given the rich schema descriptions.

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 coverage is 100% and each of the three parameters is documented, including the repo_path hash fallback and user_slug choice. The description only reinforces the git_remote path for project_key derivation and adds no syntax, precedence, or format detail beyond the schema.

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?

Uses specific verbs ('derive', 'return') on a named resource ('project_key', 'rule block'), so the agent knows it computes a key and hands back config text rather than mutating state. It does not explicitly differentiate itself from siblings like agent_onboarding or create_skill, which keeps it short of a 5.

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?

Usage is only implied: 'for local agent config files' suggests it belongs in project setup/onboarding flows, but the description never states when to call it versus alternatives or what prerequisites exist. There are no exclusions or named alternatives, so an agent must infer the context.

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.