Skip to main content
Glama

Inspect Style Specification (format.txt)

inspect_preset

Retrieve the complete format.txt typography specification for a chosen preset to verify fonts, spacing, and layout rules before Markdown-to-Word conversion.

Instructions

Inspect the full format.txt typography specification for a given preset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "preset": "<preset>"
    },
    "name": "inspect_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. Beyond the word "Inspect" implying a read, it says nothing about whether the preset must exist, what happens on an unknown preset, or the size/shape of the "full" specification; the output schema covers return values but not failure or side-effect behavior.

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 front-loaded sentence with no filler or redundancy. It is efficient, but its brevity comes at the cost of substance rather than reflecting deliberate compression of richer content.

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?

Placeholder.

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% for the single required parameter, so the schema provides only the name "preset" and a bare string type. The description repeats "for a given preset" without explaining the identifier format, case sensitivity, or how to enumerate valid values, leaving the only parameter effectively undocumented.

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?

Specific verb ("Inspect") plus a specific resource ("the full format.txt typography specification") scoped to "a given preset." It is distinguishable from list_presets and compile_markdown, though it never explicitly contrasts itself with them.

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 when-to-use guidance, no prerequisite (e.g. that the preset must already exist or how to obtain a valid name), and no mention of alternatives such as list_presets for discovering presets. Usage is only implied by the phrase "for a given preset."

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