Skip to main content
Glama
Sign In
CarryMem

CarryMem

by lulin70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

onboard

Onboards first-time users by delivering a welcome message and collecting key preferences to initialize a personalized CarryMem profile.

Instructions

First-time user onboarding. Returns a welcome message and asks key preference questions to initialize your CarryMem profile. Call this when a new user starts their first conversation.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage for the onboarding messageen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It mentions returning a welcome message and asking questions but does not disclose side effects like whether it modifies user state or if it's idempotent. For a tool that initializes a profile, this is a significant gap.

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 clear, front-loaded sentences with no extraneous information. Every word contributes to understanding the tool's purpose and usage.

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?

Given the simplicity of the tool (one optional parameter, no output schema), the description is fairly complete. It could mention that it's a one-time operation, but overall it provides adequate context for an agent to use it correctly.

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% for the single parameter 'language'. The description adds no extra meaning beyond what the schema already provides, so it meets the baseline expectation.

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?

The description clearly indicates it's for first-time user onboarding, specifying it returns a welcome message and asks preference questions to initialize the profile. This distinguishes it from sibling tools that handle existing user operations.

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?

The description explicitly states 'Call this when a new user starts their first conversation,' providing clear guidance on when to use. It does not mention when not to use or alternatives, but the context is sufficient.

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

Deploy Server

Other Tools