Skip to main content
Glama

get_services

Read-only

Lists top-level services in a Roblox place, such as Workspace and ReplicatedStorage, to help you orient in an unfamiliar project before inspecting a specific service.

Instructions

List the top-level services of the open place (Workspace, ReplicatedStorage, StarterGui and so on). Read-only. Use it to orient in an unfamiliar place, then get_tree on the service you care about.

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

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's "Read-only" merely restates that. It does disclose the result scope (top-level services only, not a recursive tree), which is useful, but says nothing about output shape or whether service objects or names are returned. With annotations covering the safety profile, this is 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each earning its place: the operation and its scope first, the safety note second, the workflow guidance third. Nothing is buried or repeated.

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 simple, zero-required-parameter read tool with rich annotations and no output schema, the description covers purpose, scope, and next step. The only gap is what the returned service entries look like, which is minor for an orientation call.

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 description coverage is 100% and the single optional place parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning about the place parameter, such as what happens when multiple places are connected beyond what the schema already states.

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?

States a specific verb and resource ("List the top-level services") and grounds it with concrete examples (Workspace, ReplicatedStorage, StarterGui). It also distinguishes itself from the sibling get_tree by framing itself as the coarse, first step before drilling into a single service.

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?

Gives explicit when-to-use guidance ("to orient in an unfamiliar place") and names the follow-up alternative (get_tree) plus the condition that selects it. It stops short of stating when this tool is unnecessary, but the intended entry-point role is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.