Skip to main content
Glama

Copybook

Find the parts a repo needs

find_snippets
Read-onlyIdempotent

Returns, word for word, the parts of a tip that meet one concise English repo need. The need is a short phrase: no code, file contents, paths or secrets. With slug, it reads that tip alone. state fit: whole blocks or named checklist sections; menu: the tip fits but no part was selected (get_tip has the whole text); none: no part selected (search_tips lists candidates). Each part carries its source line, the tip URL with a mark that check_installed reads later, and its durability, check age and models and conflicts_with. Missing metadata means unknown.

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": {
      "need": "<need>"
    },
    "name": "find_snippets"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesOne concise English task, up to 200 characters, e.g. limit unrelated code edits. Omit repo/framework details unless essential. Never code, file contents, paths or secrets.
slugNoOptional: a tip already chosen, from a search card, to answer for that tip alone.

Output Schema

NameRequiredDescriptionDefault
tipYes
menuYes
partsYes
stateYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the tip URL carries a mark that check_installed reads later (a cross-tool dependency) and that missing metadata means unknown rather than absent.

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 front-loaded with the core behavior, but the middle section is a dense run-on of state labels ('state fit:', 'menu:', 'none:') and the closing sentence enumerates return fields that the output schema already covers. Several clauses could be trimmed without losing meaning.

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?

For a two-parameter read tool with an output schema and full annotation coverage, the description covers what an agent needs: input shape, state outcomes, and which sibling to fall back to. The enumeration of returned fields is redundant with the output schema rather than a 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 coverage is 100%, so both parameters are already documented, including the 'no code, paths or secrets' constraint that the description repeats. The only marginal addition is workflow context that slug comes from a search card; baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource: it 'returns, word for word, the parts of a tip' that meet a stated repo need, which distinguishes it from get_tip (whole text) and search_tips (candidate list). The only drag is the reliance on domain jargon ('tip', 'part', 'state') that an agent must infer from context.

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?

It names concrete alternatives with conditions: on 'menu' state, get_tip has the whole text; on 'none', search_tips lists candidates; with slug, it reads that tip alone. The guidance is delivered through state enumeration rather than a direct 'use this when / not when' rule, but an agent can still route correctly.

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