Skip to main content
Glama

my_styles

Read-onlyIdempotent

List your own art styles with IDs, tokens and ratings, plus any style job in progress, so you can use, fix, rate or delete a style.

Instructions

Read-only: the person's own art styles (ones Claude built for them in Dinoctor) with id, name, a short about, tokens used and their star rating, plus the style job running now (building or fixing, with progress). Use an id with use_style, fix_style, rate_style or delete_style. Built-in styles are listed by list_styles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the marginal burden is low, but the description adds genuinely new behavior: the response also surfaces the currently running style job including whether it is building or fixing and its progress. It does not discuss result ordering, pagination, or what an empty style list looks like, which keeps it from a 5.

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 sentences, front-loaded with the read-only nature and the returned fields, then the follow-on tool routing. Every clause carries information an agent needs; nothing is redundant with the tool name or annotations.

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 carries the full burden of describing the return shape, and it does so field by field, including the live job status. Combined with zero parameters and full annotation coverage, an agent has everything required to call it and interpret the result.

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 nothing for the description to disambiguate; baseline 4 applies. The mention of 'an id' refers to fields in the response, not inputs, and does not mislead.

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?

The description names the specific resource ('the person's own art styles') and enumerates exactly what each entry contains (id, name, short about, tokens used, star rating) plus the in-flight style job with progress. It explicitly distinguishes itself from list_styles, which returns built-in styles, so an agent can tell the two apart without opening either schema.

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?

It states the concrete next step ('Use an id with use_style, fix_style, rate_style or delete_style') and routes the agent elsewhere when the target is a built-in style ('Built-in styles are listed by list_styles'). That is explicit when-to-use and alternative-selection guidance rather than implied context.

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