Skip to main content
Glama

claw.mobile AI tools catalogue

Get one tool

get_tool
Read-only

Full record for one tool by slug (e.g. "cursor", "lovable", "claude-code"): plans, prices, features, pros, cons, rating (null if unrated), price source, vendor website and claw.mobile page. Same data as GET https://claw.mobile/api/tools/{slug}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTool slug, as returned by list_tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 genuinely useful detail beyond that — the enumerated return fields and the note that rating may be null if unrated — but says nothing about what happens with an unknown slug (error vs empty result).

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 compact sentences with the identity and return payload front-loaded. The closing REST-endpoint parity note is mostly redundant but cheap and arguably useful for agents mapping to a known HTTP API.

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 correctly takes on the burden of describing return fields and the null-rating edge case, which is exactly what an agent needs. Only the failure behavior for an invalid slug is left unstated.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by giving concrete slug format examples ('cursor', 'lovable', 'claude-code'), which clarifies the expected string shape.

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?

States a specific verb+resource: 'Full record for one tool by slug', and names the record's contents. It is clearly a single-item fetch, distinguishable from list-style siblings, though it never explicitly contrasts itself with find_tool or tool_pricing.

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?

No when-to-use or when-not-to-use guidance. The only routing hint ('slug, as returned by list_tools') lives in the schema, not the description, and there is no mention of when an agent should prefer find_tool or compare_tools instead.

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