Skip to main content
Glama

Velvet Developer Docs

Velvet toy kinds and limits

get_toy_kinds
Read-only

The four Velvet toy kinds (vibration, dual motor, suction, heat), which models fall under each, a capability-checked example call per kind, and the SDK command limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope content by enumerating exactly what the payload contains, including capability-checked example calls, but says nothing further about whether examples are illustrative versus executable or how the material is organized.

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?

One compact sentence that front-loads the most important fact (the four kinds are enumerated) and then lists the remaining payload sections. It is efficient, though the enumerated content list is dense and slightly bullet-like rather than plainly structured.

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 zero-argument static lookup with no output schema, the description fully enumerates the returned sections, which is what an agent needs to decide whether the call answers its question. It falls short only on where this fits relative to the sibling doc tools.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies the call is parameterless by presenting it as a fixed reference set.

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 names the exact content set: the four Velvet toy kinds (vibration, dual motor, suction, heat), the models under each, a worked example call per kind, and SDK command limits. That is specific enough to distinguish this reference lookup from a generic doc fetch, though the verb is only implied ('the four ... kinds') rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of the sibling tools (get_doc, search_docs, get_recipes). An agent learns what the tool returns but not the condition that selects it, e.g. 'call this before building a Velvet command payload, rather than searching docs.'

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