Skip to main content
Glama

List headshot styles

list_headshot_styles
Read-only

Curated headshot styles (use id as style_item_id) and the control vocabulary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds a small amount of behavioral context by disclosing that the result includes an identifier to reuse and a 'control vocabulary', but it does not explain that vocabulary or how the returned values should be consumed.

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?

A single short sentence with no filler, and the most actionable detail (the id-to-style_item_id mapping) is included rather than buried. The phrase 'control vocabulary' is unexplained jargon that slightly undercuts the otherwise tight phrasing.

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 read-only list tool with an output schema that documents return values, the description covers what the agent needs to invoke it and how to reuse the returned id. The only real gap is that 'control vocabulary' is never explained, forcing the agent to inspect the response to understand it.

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 and the baseline of 4 applies. The mention of `id` and `style_item_id` is a useful cross-reference even though it describes outputs rather than inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (curated headshot styles) but contains no verb, relying on the title 'List headshot styles' to convey the listing action. The trailing phrase 'and the control vocabulary' is ambiguous about what is actually returned alongside the styles, leaving the purpose only partially clear.

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?

There is an implicit routing hint in 'use `id` as `style_item_id`', which tells the agent this is an enumeration step feeding a downstream headshot call. Beyond that first-person-parenthetical, there is no explicit statement of when to call this versus siblings or any precondition for doing so.

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