Skip to main content
Glama

Copybook

Find a tip

search_tips
Read-onlyIdempotent

Searches Copybook's catalog of prompts, rules, skills and setups for coding agents by an English task, with optional kind, topic and tool filters (list_facets lists their values). sort: saves orders by most saved; the default is relevance with a query and newest without. Returns compact cards with the exact paste text, dated saves and the latest check. state: match passes lexical checks, not verified suitability; related can still fit; none means no card. get_tip returns a whole tip; find_snippets(need, slug) returns the parts of one tip a repo needs.

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

Input Schema

NameRequiredDescriptionDefault
kindNoKind id: prompt, rules, skill, plugin, mcp, subagent, command or config; list_facets gives names and counts.
sortNoOrder: relevance with a query, newest without (defaults); saves means most saved on X.
toolNoTool id: claude-code, codex, cursor, pi, grok, gemini or any; list_facets gives current counts.
limitNoMaximum number of candidates: 1 to 20, default 3. Candidates can be uncertain; check state.
queryNoWords or a request in English, up to 200 characters; leave out to list by sort.
topicNoTopic id: repo (Codebase), review (Review), design (Design), long-runs (Long runs), models (Models and cost), ship (Launch), writing (Writing).

Output Schema

NameRequiredDescriptionDefault
langYes
sortYes
tipsYes
stateYes
matchesYes
messageYes
candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no repeating. The description adds genuine behavior beyond that: results are compact cards containing exact paste text, dated saves and the latest check, and the state field distinguishes lexical matches from verified suitability, including that a card may be absent. It stops short of describing result count behavior or what the latest check entails.

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?

Front-loads purpose, then filters, then ordering, then return shape, then sibling routing — a sensible priority order with no filler. A few clauses are compressed into near-telegraphic phrasing ("saves orders by most saved") that costs a re-read but carries real information.

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?

Six optional parameters, an output schema, and full annotations are all accounted for: the description covers filter discovery, ordering defaults, uncertainty in results, and where to go for full or partial retrieval. An agent has everything needed to call it correctly on the first attempt.

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% and four params are enums with documented values, so the baseline is already 3. The description still adds meaning the schema lacks: the sort default is conditional on whether a query is supplied, list_facets is the way to enumerate facet values, and limit admits uncertain candidates that should be re-checked via state.

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?

Opens with a specific verb and resource: "Searches Copybook's catalog of prompts, rules, skills and setups for coding agents by an English task", plus the optional filter set. It explicitly separates itself from get_tip ("returns a whole tip") and find_snippets ("returns the parts of one tip a repo needs"), so an agent can route between the three without opening a 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?

Names alternatives and the conditions that select them: list_facets to discover kind/topic/tool values, get_tip for one whole tip, find_snippets when only a repo-relevant slice is needed. It also gives the sort default rule (relevance with a query, newest without), which is real when-to-use guidance rather than restated schema.

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