Skip to main content
Glama
UserClimb

UserClimb

by thomaslrw

Find the right playbook

find_app_type
Read-only

Matches a product description to one of 12 app-type marketing playbooks so you can identify the right growth tactics and content guidance.

Instructions

Matches a product to one of 12 app type playbooks (habits, fitness, money, style, utilities, social and dating, learning, games, founder and dev tools, creator and business tools, family and pets, marketplaces). Pass a plain description of what the product does and who it's for.

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": {
      "description": "<description>"
    },
    "name": "find_app_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesWhat the app or product does and who it's for, in a sentence or two.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 real context beyond that: the closed set of 12 possible results, which effectively discloses the output domain absent an output schema. It does not say what happens with ambiguous or out-of-scope input, so it stops short of full disclosure.

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 core action and scope before the invocation note. The 12-item parenthetical is long but earns its place by defining the possible outcomes; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 classifier with no output schema, the description covers the input form and the result set. It is incomplete on the handoff: an agent is not told how the matched app type is consumed by siblings such as get_playbook, which is the natural next step.

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% with a single well-described parameter, so the baseline is 3. The description adds a small but meaningful nuance by calling for a 'plain description' of what the product does and who it's for, signalling free-form natural language rather than keywords or structured fields.

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 ('Matches') and resource ('one of 12 app type playbooks'), and enumerates the taxonomy so the agent knows the output domain. It is distinguishable from get_playbook by the 'matches a product' framing, but it never says explicitly that this is the classification step rather than the retrieval step, leaving room for confusion.

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?

Tells the agent HOW to invoke it ('Pass a plain description of what the product does and who it's for') but gives no when-to-use vs when-not guidance, no prerequisites, and no follow-up guidance such as using the resulting app type with get_playbook. Usage is implied rather than prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.