Skip to main content
Glama

Copybook

Read the complete tip

get_tip
Read-onlyIdempotent

Returns one complete tip: its exact Copy assets, three steps, notes, dated saves, latest check, playbooks and related slugs. Takes a slug, a Copybook or voxyz.ai tip URL (English or Chinese) or an X/twitter.com post URL, so a known reference needs no search. An unknown reference returns uncertain suggestions. Install IDs and source lines come from find_snippets; get_tip has none.

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_tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA slug, a copybook.page or voxyz.ai tip URL in either language, or the tip's X/twitter.com post URL. Known hosts also work without https://.

Output Schema

NameRequiredDescriptionDefault
tipYes
foundYes
messageYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add context — and it does: it discloses fuzzy/uncertain resolution for unknown references and explicitly scopes out install IDs and source lines as belonging to find_snippets. It does not discuss error cases or how uncertain suggestions are ranked, but the added disclosure is substantive.

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?

Three tight sentences, front-loaded with the return payload before the input and the scope limits. Dense but every sentence carries information; the field enumeration is long but functional.

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 an output schema present, the description needn't explain return structure, yet it summarizes contents anyway, and annotations plus full schema coverage handle safety and input formats. Complete enough to invoke correctly; only failure-mode behavior is left implicit.

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 coverage is 100% and the schema description already documents accepted forms (slug, copybook.page/voxyz.ai URLs in either language, X/Twitter post URL, host without https://). The description largely restates this, adding only the practical note that a known reference avoids searching. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Returns one complete tip") and then enumerates the payload (Copy assets, three steps, notes, dated saves, latest check, playbooks, related slugs). This is clearly a single-record fetch, distinct from the sibling search/find tools without needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says a known reference "needs no search", implying the fetch-vs-search decision, and names find_snippets as the alternative for install IDs and source lines. The when-not path is present but indirect: it only says an unknown reference "returns uncertain suggestions" rather than naming search_tips as the fallback.

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