Skip to main content
Glama

Managed Nerds

list_projects

Read-onlyIdempotent

Managed Nerds' fixed-scope projects (business email, domains, Wi-Fi, Google Business Profile, websites, security and more) and how to ask for each: who it's for and isn't, what's included, what the buyer provides, typical timeline, whether it's one-time or ongoing, and the questions a quote needs. Every project is quoted by a person; no prices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — results are descriptive project briefs with no pricing, and quoting is human — but says nothing about result volume, pagination, or ordering.

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 that front-loads the resource and then lists the attributes each entry carries. The parenthetical project list and the colon-separated attribute list are efficient, though the sentence is long and slightly overloaded.

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?

With no parameters, no output schema and a fully declared read-only annotation set, the description's job is to say what comes back and what does not — it does both, spelling out the per-project attributes (audience, inclusions, buyer inputs, timeline, one-time vs ongoing, quote questions) and stating explicitly that no prices are returned.

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 the baseline of 4 applies; there is no argument semantics for the description to compensate for.

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 a specific resource — 'Managed Nerds' fixed-scope projects' — and enumerates concrete project types (business email, domains, Wi-Fi, Google Business Profile, websites, security), so an agent knows what catalog it gets back. It lacks an explicit verb ('list'/'returns') and never differentiates itself from siblings such as list_services or list_guides, leaving that distinction to inference.

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?

There is no statement of when to call this versus alternatives, no preconditions, and no exclusions. The only adjacent guidance is 'Every project is quoted by a person; no prices', which describes output content rather than usage context.

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