Skip to main content
Glama

List Built-in Style Presets

list_presets

Lists built-in style presets with typography specifications for Simplified/Traditional Chinese Academic, Tech Report, and Nature English Paper, helping users choose the right document format.

Instructions

List all available built-in style presets (Simplified/Traditional Chinese Academic, Tech Report, Nature English Paper) with typography specifications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool lists built-in presets and includes typography specifications, which implies a read-only operation. However, it does not explicitly state that the operation is non-destructive, requires no permissions, or has any other behavioral constraints.

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 description is a single front-loaded sentence with no unnecessary wording. It states the action, scope, examples, and returned metadata efficiently.

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?

This is a simple, parameterless listing tool with an output schema, so the return values need not be explained in detail. The description names the preset families and mentions typography specifications, which is sufficient context for an agent to decide whether to call it. It could be slightly more complete by stating that the list is read-only or that it excludes custom presets, but overall it is adequate.

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 has zero parameters, so there is no parameter meaning for the description to add. The baseline for a parameterless tool is 4.

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 states a specific verb and resource: 'List all available built-in style presets.' It also names example preset families and mentions typography specifications, making the scope clear. It does not explicitly contrast with inspect_preset, but the word 'all' distinguishes this listing tool from a single-preset inspection tool.

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: an agent should call this when it needs to discover available presets. There is no explicit guidance about when not to use it or when to use inspect_preset instead, so the guidance is adequate but clearly incomplete.

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