Skip to main content
Glama

Start here — what can this MCP server do?

get_started
Read-onlyIdempotent

Call this for a greeting (hi, hello), a connectivity/liveness test, 'what can you do', or any message too general to match a specific tool below. Returns the full menu of real questions this server answers, each mapped to the tool name that answers it, so the next call can go straight to the right tool.

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
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "report": {
      -      "description": "The full human-readable report.",
      -      "type": "string"
      -    },
      -    "source": {
      -      "description": "Canonical engineeringleaders.io page this answer is derived from.",
      -      "type": "string"
      -    },
      -    "verdict": {
      -      "description": "Headline verdict, when the tool returns one.",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "report",
      -    "source"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • removedInput schema / required
      Removed value: -[
      -  "context"
      -]
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description adds the useful non-obvious fact that the response is a catalog mapping questions to tool names — the key behavioral detail given there is no output schema. It stops short of describing response size or format, which keeps it from a 5.

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?

One front-loaded sentence covering triggers first, then return value, with no filler. Every clause (greeting, liveness, capability query, unmatched fallback) carries distinct routing information.

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 zero-required-parameter, read-only, no-output-schema discovery tool, the description supplies everything an agent needs: when to call it, what it returns, and how to use the result to route the next call. Nothing material is missing.

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 coverage is 100% and the single optional 'context' parameter is fully documented in the schema, including that it never changes the answer. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work here.

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?

Names a specific behavior set — greeting, connectivity/liveness test, 'what can you do' capability query, and catch-all for unmatched messages — plus the concrete payload ('full menu of real questions... mapped to the tool name'). This clearly separates it from the domain siblings like get_engineering_leadership_benchmarks, which answer specific questions rather than enumerate them.

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?

Gives explicit positive triggers (greeting, hello, liveness check, 'what can you do') and an explicit routing rule for the negative case: any message too general to match a specific tool. It also tells the agent the intended follow-up ('the next call can go straight to the right tool'), so the when-to-use decision is fully specified.

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.