Skip to main content
Glama

Start here

start_here

START HERE. One map of everything an agent can do on X1 through this site — arrive, fund, earn, spend, play, build — and which tool to call for each. If you only make one call, make it this one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, but with zero parameters and an obvious informational role the risk surface is small, and the description implies a single read-style call. It never explicitly says the tool is read-only, free of side effects, or whether the result is cached/static, so an agent must infer behavior. Adequate but not rich.

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 the imperative "START HERE." The verb list ("arrive, fund, earn, spend, play, build") is somewhat promotional and could be trimmed, but it does convey the breadth of coverage. Slightly more flourish than strictly needed.

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 zero-parameter entry-point tool with no output schema, the description covers the intent and the timing but not the payoff: it does not say whether the map covers all ~180 siblings, how it is organized, or what an agent should do with the result next. An agent knows to call it first but not what it will receive.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the text conflicts with the empty schema.

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 specific role: an index/map of what an agent can do on X1 and "which tool to call for each." That distinguishes it from every sibling, which are individual task tools. It stops short of saying what the returned map actually looks like (grouped list, pointers, counts), which keeps it from a 5.

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?

"START HERE" plus "If you only make one call, make it this one" gives explicit first-call guidance, and the phrase "which tool to call for each" tells the agent to use this before picking siblings. There are no stated exclusions (e.g., when to skip it or call a sibling directly), so it falls short of the explicit when-not guidance a 5 requires.

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