Skip to main content
Glama

claw.mobile AI tools catalogue

List AI building tools

list_tools
Read-only

List the tools in the claw.mobile catalogue (33 AI app builders, AI IDEs, terminal agents and coding assistants) with plans, prices and price provenance. Optional filters: type and free (true = only tools with a free plan, false = only tools without one). Same data as GET https://claw.mobile/api/tools.

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
freeNotrue: only tools with a free plan; false: only tools without one
typeNoTool type: ai-ide (AI IDE), app-builder (App Builder), terminal-agent (Terminal Agent), assistant (Assistant), specialized (Specialized)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds non-obvious value by stating what each record carries (plans, prices, price provenance) and that the data is identical to the public GET endpoint. It stops short of stating whether all 33 records come back in one response or whether results are paged or ordered.

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 scope, then the filters; nothing is buried or padded. The minor cost is that the filter sentence largely duplicates the schema text, but it is short enough not to be wasteful.

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?

With no output schema, the description is the only source of return-value information, and it does name the fields returned plus the catalogue size. For a simple two-optional-parameter list tool that is nearly sufficient; only ordering and page/size behavior remain unspecified.

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 both parameters already carry descriptions, including the free=true/free=false polarity and the enum label mapping. The description restates the same filter semantics without adding anything the schema lacks (e.g. whether filters combine with AND), so the baseline 3 applies.

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?

"List the tools in the claw.mobile catalogue" gives a specific verb plus resource, and the parenthetical (33 AI app builders, AI IDEs, terminal agents, coding assistants) bounds what kind of records come back. It does not name a sibling such as find_tool or get_tool as the alternative for narrower lookups, so the agent must infer the distinction from names alone.

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 description explains the two optional filters and their boolean polarity, which implies the browsing/enumeration use case (no query term, no single tool specified). It never says when to prefer this over find_tool or compare_tools, and it gives no exclusion criteria, so selection guidance is implied rather than stated.

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