Skip to main content
Glama

memory_onboarding_guide

Read-only

Retrieves an integration guide for generic, Kiro, or Claude Code clients, helping users configure the MCP Memory Service for their setup.

Instructions

Get integration guide for a specific client type.

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

Input Schema

NameRequiredDescriptionDefault
client_typeNoClient type (generic, kiro, claude-code)generic

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv13.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't say what the guide contains, how long it is, whether output is markdown or structured, or what happens for an unsupported client_type value (the schema lists only generic/kiro/claude-code but doesn't constrain it as an enum).

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?

A single front-loaded sentence with no redundant wording. It is efficient, though the brevity tips into under-specification rather than crispness.

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

Completeness3/5

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

For a one-parameter read-only tool with full schema coverage and annotations, this is minimally adequate. Still missing is any sense of what the returned guide is for or how it should be used, and no output schema exists to fill that gap.

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 the single parameter has its own description listing the accepted client types, so the schema does the heavy lifting. The description's phrase 'a specific client type' merely echoes the parameter without adding meaning, which is the baseline 3 case.

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 ('Get') and resource ('integration guide') scoped to a client type, so an agent knows what the tool returns. It doesn't distinguish itself from any sibling, though the memory_* siblings in the catalog are clearly a different domain, so the ambiguity risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this versus other tools, no prerequisites, and no mention of the 'generic' default or when to prefer a specific client_type. The usage context is only implied by the tool name.

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