Skip to main content
Glama

List services

list_services
Read-only

List the engineering services status403 offers — web scraping, reverse engineering, web3 and dApp engineering, and backend, frontend, and infrastructure engineering for new builds or existing systems — with what each one covers and the anchor link to its section on the page. Pass a query to keep only the services matching a keyword such as "scraping" or "anti-bot".

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
queryNoOptional keyword to filter by. Omit to list every service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine value by disclosing the return shape (each service's coverage and its anchor link), which matters since there is no output schema. It says nothing about ordering, pagination, or whether anchor links are relative, so it stops short of rich behavioral context.

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?

Two sentences, front-loaded with the resource and its contents before the filtering instruction. The long service enumeration is somewhat list-heavy but arguably earns its place by telling the agent what the catalog contains.

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 one-parameter, read-only listing tool with no output schema, the description covers purpose, filter behavior, and the shape of returned items. Minor omissions such as result ordering or link format are not blocking for correct invocation.

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 coverage is 100% and the schema already states the parameter is an optional keyword filter that lists everything when omitted. The description only adds illustrative keyword examples, which is marginal value over the structured field, so the baseline 3 applies.

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 (List) and resource (engineering services offered), and goes further by enumerating the service categories and what the response contains (coverage plus anchor link). This is clearly distinguishable from siblings like read_page or search_blog, which operate on page/blog content rather than a service catalog.

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

Usage Guidelines3/5

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

The second sentence explains how to narrow results with a keyword and gives concrete examples ('scraping', 'anti-bot'), which is useful invocation guidance. However, there is no explicit statement of when to prefer this tool over answer_common_question or read_page, and no exclusions or prerequisites.

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