Skip to main content
Glama

list_tools

Read-onlyIdempotent

List the five free, client-side cloud & security browser tools (including WebMCP-enabled utilities like GCP IAM Policy Checker, Compute Selector, Database Selector, Cron Translator, and JWT Analyzer) available on alekseialeinikov.com. Use this instead of search_articles when a user wants an interactive calculator, policy checker, or parser rather than an article. The optional lang parameter localizes the returned hub and tool URLs ("en" default, or "de"). Read-only, unauthenticated, no side effects, static payload, subject to a 30 req/min per-IP rate limit.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage prefix for returned tool hub and tool page URLs ("en" for English, "de" for German; defaults to "en").en

Output Schema

NameRequiredDescriptionDefault
toolsYesList of available client-side browser tools.
hubUrlYesLocalized tools hub URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / lang / default
      Added value: +"en"
    • addedInput schema / properties / lang / description
      Added value: +"Language prefix for returned tool hub and tool page URLs (\"en\" for English, \"de\" for German; defaults to \"en\")."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "hubUrl": {
      +      "description": "Localized tools hub URL.",
      +      "type": "string"
      +    },
      +    "tools": {
      +      "description": "List of available client-side browser tools.",
      +      "items": {
      +        "properties": {
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "hubUrl",
      +    "tools"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, but the description adds information annotations cannot carry: the payload is static, no authentication is required, and there is a 30 req/min per-IP rate limit. That rate limit is exactly the kind of operational constraint an agent needs before retry-looping.

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 front-loaded with purpose, then routing guidance, then operational facts, and nothing is wasted. The parenthetical tool enumeration is long but justified because it tells the agent what the payload contains.

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?

The tool is simple, an output schema exists so return values need no prose, and the description still covers scope, routing, localization, auth, and rate limits. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the single lang parameter already documents the enum, default, and that it prefixes returned hub and tool URLs. The description's note that lang localizes 'the returned hub and tool URLs' largely restates the schema, so it earns baseline rather than extra credit.

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 opens with a specific verb and resource ('List the five free, client-side cloud & security browser tools') and enumerates the actual tools returned, so an agent knows exactly what comes back without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: use this instead of search_articles when the user wants an interactive calculator, policy checker, or parser rather than an article. That is a named alternative plus the condition that selects it.

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