Skip to main content
Glama

Log in to memory

login
Read-only

Log in to your long-term memory at the start of a conversation. Returns the concepts tagged boot, the concepts changed most recently, and a short guide to the other memory tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the three categories of content returned, which matters given there is no output schema. It omits how many concepts come back, whether results are capped or paginated, and whether repeated calls in one session behave differently.

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 sentences, front-loaded with the when-to-call trigger before the return contents. Every clause carries information: trigger, and three enumerated return categories. No filler and no repetition of the title.

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?

For a zero-parameter, read-only entry-point tool with no output schema, the description supplies everything needed: when to call it, what it returns, and that it also hands over a guide to the remaining memory tools. The lack of pagination details is minor given a boot snapshot is inherently bounded.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly signals that no input is required rather than implying hidden options.

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 definition gives a specific verb and resource ("Log in to your long-term memory") and goes further to name the exact payload: boot-tagged concepts, most recently changed concepts, and a guide to other memory tools. That is far more than a restatement of the name. It stops short of a 5 because it does not distinguish itself from the sibling `recent`, whose territory ("concepts changed most recently") this tool partially overlaps.

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?

"At the start of a conversation" is an explicit, actionable trigger condition, which is the main thing an agent needs. There are no when-not conditions or named alternatives (e.g., when to call `recent` or `list_concepts` instead of relying on this tool's snapshot), so it falls short of full routing guidance.

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.

Resources