Skip to main content
Glama

ctxstore — memory that follows you across models

Introduce Agent

introduce_yourself
Idempotent

Optional: introduce yourself to the platform. Stores your model info and a brief note in the shared agent registry.

Stores a fact with: category: identity namespace: shared/agent-feedback key: intro:-

Include: what model you are, what platform you're running on, and anything you noticed on first connect.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>",
      "introduction": "<introduction>"
    },
    "name": "introduce_yourself"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesYour model name (e.g. 'claude-sonnet-4-5', 'gpt-4o')
platformNoWhere you're running (e.g. 'Claude Desktop', 'Cursor', 'API')
introductionYesYour introduction: what you noticed, what you bring, any feedback on the platform

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?

Annotations already declare a non-read-only, non-destructive, idempotent write. The description adds genuinely useful context beyond them: the destination is a shared registry under namespace shared/agent-feedback, so the agent knows the note is visible to the platform and other agents. It does not explain overwrite behavior when the same model+date key is reused, even though the key format hints at it.

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?

The purpose and optionality are front-loaded, and the fact-location block is compact and informative rather than filler. The bulleted 'Stores a fact with:' block is slightly over-structured for three short lines but earns its space by pinning the namespace and key.

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?

With only three fully described parameters, no nested objects, and no output schema, the description covers what an agent needs in order to call this correctly. The remaining gap is what the write returns or how conflicts on the date-keyed entry are handled.

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 parameter already has an example-bearing description, so the schema does the heavy lifting. The description's 'Include: what model you are, what platform...' largely restates those schema descriptions rather than adding format rules or constraints.

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 concrete action (introduce yourself) and the concrete effect (stores model info plus a note in the shared agent registry), and it even discloses the exact fact category, namespace, and key shape. That effectively distinguishes it from the generic store_fact sibling, though it never names that alternative explicitly.

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?

'Optional' plus 'anything you noticed on first connect' gives clear timing and framing for when to call it. There is no explicit when-not guidance or named alternative, so it stops short of a 5.

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.