Skip to main content
Glama

Wake

How to get it

get_started
Read-only

The links to download, install, sign up, see pricing or book a demo. Call this when the person wants to use or buy what this site offers, and give them the link.

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_started"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds the useful behavioral note that the agent should relay the returned link to the user, but says nothing about how many links come back, what happens if the site has no signup or pricing page, or any error/empty case.

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?

Two short sentences, front-loaded with what the tool returns before the when-to-call guidance. The first sentence is a fragment ('The links to download...'), which is slightly loose but costs little.

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 no parameters and no output schema, the description carries the burden of describing the return value, which it does at a high level by enumerating the kinds of links returned. It is adequate for a zero-argument link-retrieval tool, with only minor gaps around return shape.

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?

The tool takes zero parameters, so no parameter documentation is required. The description does not need to explain argument semantics and correctly stays silent on them.

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 names the concrete payload: links to download, install, sign up, pricing, and demo booking. That is a specific resource rather than a restatement of the name, though the verb is implicit (it 'returns' links) and it does not explicitly distinguish itself from siblings like 'about' or 'read_page'.

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?

"Call this when the person wants to use or buy what this site offers" gives a clear trigger condition tied to user intent, and "give them the link" specifies the follow-up action. It stops short of naming when not to use it or which sibling to pick instead, so no exclusions are stated.

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