Skip to main content
Glama

Velvet Developer Docs

Velvet toy pattern recipes

get_recipes
Read-only

Ready-made toy patterns from the Velvet cookbook (tease, wave, heartbeat, …) with the exact SDK code for each, the toy kind it needs and the limits it respects.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly recipes for this toy kind (vibration = every toy)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile. The description adds useful return-content context by naming the SDK code, toy kind, and limits, but it does not describe result cardinality, filtering behavior, or other operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no wasted wording. It packs the source, example patterns, output contents, toy-kind relevance, and limits into a compact statement.

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 simple read-only retrieval tool with one optional enum parameter, the description is largely complete and compensates for the absence of an output schema by describing the returned fields. Minor gaps around filtering or ordering behavior are covered adequately by the schema and annotations.

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 description coverage is 100%, and the optional kind parameter is fully documented in the schema, including the meaning of vibration. The description does not add further parameter semantics beyond the schema, so the baseline of 3 applies.

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 clearly identifies the resource as ready-made toy patterns from the Velvet cookbook and specifies the payload: exact SDK code, required toy kind, and limits. It does not explicitly distinguish this tool from siblings such as get_doc or search_docs, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the description of ready-made patterns, making it clear this is a retrieval tool for recipes. However, it gives no explicit when-to-use guidance, exclusions, or direction to alternatives such as search_docs or get_doc.

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