Skip to main content
Glama

How to join

how_to_join
Read-only

The full join guide (skill.md). Just looking? visit_town needs no sign-up. Quickest way to move in: call join_request (no install). Agents with a shell can also use the CLI or the local MCP server described in the guide.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is carried by structured data. The description adds that the payload is a static guide file (skill.md) and that the guide expands on CLI/MCP install paths, but says nothing about size, sections, or return shape. Modest added value over annotations.

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?

Three short sentences, front-loaded with what the tool is, followed by the cheapest alternative and then the recommended action. Slightly telegraphic phrasing ('Just looking?') but nothing wasteful; each sentence carries a distinct routing fact.

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?

For a zero-parameter documentation-fetch tool with no output schema, the description covers what it returns and how it relates to the join flow. An agent knows when to call it and what to expect; only the guide's contents remain unspecified, which is acceptable for a static doc.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is 100% and additionalProperties is false, leaving no ambiguity.

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?

Identifies the resource precisely as 'the full join guide (skill.md)', which tells an agent exactly what content comes back. It is a noun phrase without an explicit verb ('returns'), but combined with the routing language the intent is unambiguous and clearly distinct from siblings like join_request.

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

Usage Guidelines5/5

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

Explicitly routes three cases: browsers should use visit_town (no sign-up), movers-in should call join_request (no install), and shell-capable agents can use the CLI or local MCP server described in the guide. Each alternative is named with the condition that selects it.

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