Skip to main content
Glama

get_services

Lists all smart services in the CloudNet cluster for monitoring and management purposes.

Instructions

List all smart services

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration: defines the 'get_services' tool with name, description, and empty input schema in the list_tools() function.
    types.Tool(
        name="get_services",
        description="List all smart services",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Tool handler: in the call_tool() function, handles 'get_services' by making a GET request to the 'service' API endpoint and returning the result as text.
    @app.call_tool()
    async def call_tool(
        name: str, arguments: dict[str, Any] | None
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        if arguments is None:
            arguments = {}
    
        if name == "get_nodes":
            data = await client.request("GET", "node")
            return [types.TextContent(type="text", text=str(data))]
        elif name == "get_node_info":
            node_id = arguments.get("node_id")
            if not node_id:
                raise ValueError("node_id is required")
            data = await client.request("GET", f"node/{node_id}")
            return [types.TextContent(type="text", text=str(data))]
        elif name == "get_services":
            data = await client.request("GET", "service")
            return [types.TextContent(type="text", text=str(data))]
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only says 'List all smart services', implying a read-only operation, but does not explicitly state that it is non-destructive, has no side effects, or any other behavioral traits. The minimal information is insufficient.

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?

The description is a single sentence with no extra words. It is front-loaded and efficient, earning its place.

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 list tool with no parameters and no output schema, the description provides the essential purpose. However, it could be slightly more complete by indicating that it returns a list of service identifiers or summaries, but the current level is adequate.

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?

There are no parameters, so the baseline score is 4. The description adds no parameter-specific information, which is acceptable given the absence of parameters.

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?

The description clearly states the action ('List') and the resource ('all smart services'), making the purpose unambiguous. It distinguishes itself from sibling list tools by specifying 'services' rather than nodes, players, or other entities.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like get_nodes or get_player_info. The description does not mention any conditions or context for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ergo042/cloudnet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server