Skip to main content
Glama

list_hairstyle_templates

Read-only

Lists YouCam's predefined hairstyle templates so agents can select options for a hairstyle try-on request. Use pagination to browse available templates.

Instructions

List YouCam's predefined hairstyle templates for try_hairstyle. Free.

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

Input Schema

NameRequiredDescriptionDefault
page_sizeNo
starting_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description's only added behavioral fact is 'Free' (a cost signal) and that the catalog is predefined/fixed, which is modest but real value beyond annotations. It discloses nothing about pagination behavior or how many templates exist per page.

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?

Two short sentences, front-loaded with the operation and resource, with no redundant restatement of the name. The trailing 'Free' fragment earns its place as a cost note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 carries the burden of explaining the return shape, yet it never says the response is a list of templates (presumably including IDs to pass to try_hairstyle) nor how paging/next-token works. For a paginated listing tool with two undocumented parameters, that is a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so nothing documents page_size or starting_token except their names and constraints. The description does not explain that these are pagination controls, how starting_token is obtained, or what happens when it is omitted, leaving the description to compensate and falling short.

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?

States a specific verb and resource ('List YouCam's predefined hairstyle templates') and ties it to the consuming tool, try_hairstyle, so an agent can distinguish it from the try-on sibling. It could be sharper only by noting what a template record contains, but the core purpose is unambiguous.

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?

The phrase 'for try_hairstyle' implies this is the discovery step preceding a try-on call, which is adequate implied usage guidance. However, there is no explicit when-to-use/when-not statement and no mention of using the returned templates as try_hairstyle inputs, so the workflow link is left to inference.

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