Skip to main content
Glama

get_onboarding_guide

Read-only

Retrieve integration guidance for a specific client type, such as generic, Kiro, or Claude Code, to connect it to the memory service.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

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 essentially nothing beyond that: it does not say what the guide contains, its format, whether unknown client types fall back to generic, or how large the response is.

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 short sentence with no filler and the key qualifier (client type) front and center. It is efficient, though very slightly under-specified rather than padded.

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 trivial read-only lookup with one optional, fully documented parameter and no output schema, this is roughly adequate. It would be stronger if it hinted at what the guide covers or how an unspecified client type is 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 description coverage is 100% and the single parameter is documented with its default (generic) and example values. The phrase "specific client type" mirrors the schema without adding format, case-sensitivity, or fallback behavior details, so the baseline of 3 applies.

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?

States a specific verb ("Get") and resource ("integration guide") scoped to a client type, so an agent knows exactly what it returns. It does not reference any sibling, but no sibling in the catalog covers onboarding/guide retrieval, so differentiation is less critical here.

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 explicit when-to-use guidance, no preconditions, and no mention of alternatives or what to do for other client types. The agent must infer that this is the tool to call when a user asks for setup/integration instructions.

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