Push Drop Stick: force-free dog training

Search the Handbook

search_handbook

Read-onlyIdempotent

Search the Push Drop Stick Handbook: 140+ short articles by a certified force-free trainer (Allison Wells, CTC). Covers how dogs learn (positive reinforcement, punishment, extinction, classical conditioning), fear and reactivity (threshold, trigger stacking, desensitization and counter-conditioning, dogs who wore shock or prong collars), teaching techniques (markers, lures, shaping, duration/distance/distraction), gear (harnesses, head halters, muzzles, why not prong or shock collars), a FAQ (treats, where and how often to train), and how the app and Coach work. Use for "what is", "why" and "should I" questions. Returns entry ids, the most relevant paragraph and canonical urls; read_handbook returns a whole entry.

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": {
      "query": "<query>"
    },
    "name": "search_handbook"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (1-25).
`query`	Yes	A question or topic, in plain words.
`section`	No	Optional: search only this section.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context about the return payload (entry ids, most relevant paragraph, canonical urls), which matters since there is no output schema. It does not discuss ranking quality or empty-result behavior, so it is solid but not rich.

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-loaded with the tool name and scope, then the topic taxonomy, then the usage rule and return shape. The topic catalog is long but earns its place by supplying query vocabulary for a search tool. Slightly list-heavy, but no filler sentences.

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?

With no output schema, the description correctly covers the return shape and points to read_handbook for full entries. All three parameters are documented in the schema, and the topic catalog plus usage rule give the agent everything needed to call it correctly.

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%, so the baseline is 3, but the description adds meaning by enumerating the topical domains (learning science, fear/reactivity, gear, FAQ, app/Coach) that map onto the section enum values, helping the agent choose a section. It does not explain limit behavior beyond what the schema states.

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 (search the Push Drop Stick Handbook) plus scope: 140+ short articles by a named certified trainer. It explicitly distinguishes itself from read_handbook by noting that this returns ids and a relevant paragraph while read_handbook returns a whole entry.

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?

Gives an explicit trigger condition — use for "what is", "why" and "should I" questions — and names the alternative tool plus the condition that selects it (fetch a whole entry). The topic catalog further tells the agent which question shapes fit.

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

All Push Drop Stick: force-free dog training tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?