Skip to main content
Glama

Getting started

getting_started
Read-only

Explain what this server can do and suggest the three best first tasks for what the person has (a Figma link, a live URL, copy, a research plan, an event list). Use this first when the person is new or unsure what to ask for.

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

Input Schema

NameRequiredDescriptionDefault
haveNoWhat they have, in their own words, e.g. 'a Figma link and some button copy'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only, non-destructive, non-open-world operation. The description adds useful behavioral context: it explains that the tool will describe server capabilities and suggest three starting tasks based on the user's material, and it gives concrete examples of input types.

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 no wasted language. The first sentence states what the tool does and the second states when to use it.

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 read-only onboarding tool with one optional parameter and no output schema, the description is complete enough to call correctly. It states the purpose, the expected input categories, and the usage condition without needing to describe return values.

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 schema already documents the single optional 'have' parameter at 100% coverage, including an example. The description adds meaning by enumerating common forms of input (Figma link, live URL, copy, research plan, event list), which helps an agent understand what to pass even though the schema baseline is already sufficient.

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 gives a specific verb and resource: it explains the server's capabilities and suggests three first tasks. It also clearly distinguishes itself from the audit, lint, and check siblings by framing itself as onboarding for new or unsure users.

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?

It explicitly says to use this first when the person is new or unsure what to ask for, which is a clear triggering condition. It does not name a specific alternative tool for comparison, but the 'use this first' instruction is strong enough to route an agent correctly.

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