Skip to main content
Glama

list_templates

Lists available note templates so you can choose a template name to pass to create_note and apply the desired note format.

Instructions

사용 가능한 노트 템플릿 목록 (wiki/.templates/*.md).

create_note(template="<이름>") 로 적용할 수 있는 양식 목록을 반환한다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the source of the data (markdown files under wiki/.templates) and that it returns a list, which implies a read-only enumeration, but it never says whether the call mutates anything, how missing or empty template directories behave, or whether all files are always returned.

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 resource and location, then the practical use. Nothing redundant and nothing padded.

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-parameter listing tool with an output schema already defining the return shape, the description covers what is needed to call it. Only edge-case behavior (empty template set, unreadable directory) is left unstated.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no parameter claims beyond the empty schema.

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?

States a specific verb and resource ('사용 가능한 노트 템플릿 목록') and even names the backing storage location (wiki/.templates/*.md). It also distinguishes itself from siblings by naming create_note as the consumer of the returned template names, so an agent can tell exactly what this returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence ties the tool to a concrete follow-up action: the returned names can be passed to create_note(template="<이름>"). That gives clear usage context, but there is no explicit statement of when not to call it or what to do if the list is empty.

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