Skip to main content
Glama

Managed Nerds

list_services

Read-onlyIdempotent

Managed Nerds' managed IT and co-managed security services, what an estimate needs, and the rules (RMM, users, Linux, US only, IT support billed separately on managed IT). No prices. Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: 'No prices' preempts an expectation the agent would otherwise form, and the enumerated rule set signals what content comes back. It does not describe pagination or response shape, 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.

Conciseness4/5

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

It is a single dense sentence with no filler, though the parenthetical rule list makes it read as a fragment rather than a structured statement. The most actionable instruction, 'Call this first,' is placed at the very end instead of being front-loaded, which slightly weakens scanning.

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 zero-parameter, read-only catalog tool with no output schema, the description covers what content is returned and the key constraint (no pricing). The phrase 'what an estimate needs' is somewhat abstract and could be sharper, but the agent has enough to call it correctly and interpret the result.

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 zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly adds nothing about inputs and instead spends its words on scope and output content.

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 specific resource it returns: managed IT and co-managed security services, the inputs an estimate requires, and the eligibility rules (RMM, users, Linux, US only, IT support billed separately). It is written as a noun phrase rather than a verb+resource, but an agent can tell it is a static catalog reader. It does not explicitly contrast itself with siblings such as list_guides or list_projects, leaving some differentiation to the name alone.

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 first' is an explicit ordering directive that tells the agent when to reach for this tool relative to everything else. There are no stated exclusions or alternatives beyond that, but the sequencing instruction is concrete and unambiguous.

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