Skip to main content
Glama

Agent Loopr

agentloopr_list_services

Read-onlyIdempotent

List Agent Loopr's services with URLs: SaaS Products, Agentic Systems, Vibe Code Rescue, and Business Brain (a team assistant built on a company's own files, with an international and an India page).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral content beyond that by specifying that URLs are included and by identifying the exact services returned, including the Business Brain variant pages.

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?

The definition is a single front-loaded sentence with no filler. The parenthetical about Business Brain is somewhat lengthy but provides useful disambiguation, so the wording largely earns 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 zero-parameter read-only list tool, the description is nearly complete: it states the resource and enumerates the returned services. Without an output schema, it could say more about the return shape, but the annotations and enumeration cover most agent needs.

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 has zero parameters, so the schema itself has no parameter semantics to explain and the baseline is 4. The description adds no parameter detail, which is appropriate here.

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 uses a specific verb and resource ('List Agent Loopr's services with URLs') and enumerates the services returned. It does not explicitly distinguish itself from siblings such as agentloopr_list_case_studies or agentloopr_get_page, so it stops short of a 5.

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?

The description describes what the tool returns but gives no explicit when-to-use guidance, exclusions, or alternatives among the sibling tools. An agent must infer that this is the browse-the-service-catalog tool.

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