Push Drop Stick: force-free dog training

Read a training plan

get_plan

Read-onlyIdempotent

The full content of one public plan: description, equipment, cues, and every step with setup, instructions, success/failure criteria, set size and the rule for moving on, plus the push/drop/stick execution rules. Pass the plan ref from search_plans or list_plans. Link the user to the returned url; plan text may be quoted with attribution to its author.

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": {
      "plan": "<plan>"
    },
    "name": "get_plan"
  }
}

Input Schema

Name	Required	Description	Default
`plan`	Yes	The `plan` ref from search_plans or list_plans: a slug (library plan) or "handle/slug".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive semantics, so the description is not required to restate safety. It nevertheless adds real behavioral context beyond them: the plan is public, results include a `url` the agent should link to, and plan text may be quoted only with attribution to `author` -- a licensing-style constraint an agent would otherwise violate.

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 the returned content, then the ref requirement, then the presentation/attribution rules -- a sensible order with no filler. The content enumeration is long but earns its place because there is no output schema.

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 takes on the burden of describing return values and does so thoroughly, plus covers input provenance and how to present results to the user. Nothing an agent needs in order to call it correctly is missing.

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 single parameter already documents the slug or "handle/slug" form. The description reinforces the ref's provenance (comes from search_plans or list_plans) but adds no parsing or format detail the schema does not already supply.

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?

Names a specific retrieval action and a specific resource (the full content of one public plan), then enumerates what that content includes: description, equipment, cues, steps with setup/instructions/criteria, set size, progression rule, and execution rules. It also implicitly separates itself from list_plans and search_plans by naming them only as the source of the ref.

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 directs the agent to pass the `plan` ref obtained from search_plans or list_plans, which encodes the intended discovery-then-fetch workflow. It stops short of stating when-not to use it (e.g., when the plan is private or when a list view suffices), so it is clear guidance without exclusions.

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?