Skip to main content
Glama
UserClimb

UserClimb

by thomaslrw

Get hook patterns

get_hooks
Read-only

Fetch hook rules, patterns, and fill-in templates for any app or a chosen app type so you can draft hooks based on proven shapes, not copied wording.

Instructions

Hook rules and patterns with [fill-ins]: what works for any app, plus the angles (pains, desires, everyday moments), patterns that work and patterns that flop for one kind of app. Use them as shapes, never word for word.

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": "get_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_typeNoOptional. Adds hooks for this kind of app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 real content scope — generic plus app-type-specific material, and negative examples ('patterns that flop') — but says nothing about return format, volume, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the content scope, but the bracketed '[fill-ins]' notation is unexplained jargon and the second clause is dense and slightly repetitive ('patterns that work and patterns that flop'). It is efficient but not maximally clear.

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?

With one optional parameter, full schema coverage, and safety annotations, most of the burden is already carried by structured fields. The description covers content well but omits what the response actually looks like or how many hooks to expect, leaving a modest gap.

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 app_type enum is documented as optional with a clear effect. The description's 'for one kind of app' loosely echoes that but adds no syntax or behavioral detail beyond the schema, so 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?

The description names the specific resource retrieved — hook rules and patterns, including angle categories (pains, desires, everyday moments) and both effective and failing patterns. The retrieval verb is implicit in the name/title rather than stated, and no sibling (e.g., get_playbook, get_video_structures) is referenced to sharpen the distinction, so it is clear but not fully differentiated.

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?

'Use them as shapes, never word for word' gives a directive about how to apply the output, which is genuinely useful. However, it never states when to call this tool versus get_playbook or get_growth_moves, so selection guidance is only implied.

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