lsth-mcp

template_get

Retrieve approved template files for a given document type, with optional filtering by market and customer.

Instructions

F4 — lấy file khuôn đã duyệt cho một loại tài liệu.

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": {
      "kind": "<kind>"
    },
    "name": "template_get"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`market`	No
`customer`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a non-mutating read operation ('lấy') and adds the useful 'approved' filtering trait, but it does not disclose error cases, authorization needs, or other behavioral details beyond what the verb itself suggests.

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?

The description is a single efficient sentence with no filler, and the core meaning is front-loaded after the brief 'F4' label. The only minor issue is that 'F4' is unexplained, though it does not prevent understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with an output schema, the description is minimally viable: an agent can infer the primary call using 'kind'. However, without semantics for market/customer and without sibling-routing guidance, the agent may not know how to use the optional parameters effectively.

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?

The description partially clarifies that 'kind' corresponds to the document type ('loại tài liệu'), but it gives no meaning for 'market' or 'customer'. Since schema description coverage is 0%, the description does not compensate enough for these two optional parameters.

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 uses a specific verb ('lấy' = get) and a specific resource ('file khuôn đã duyệt' = approved template file), scoped to a document type. It distinguishes the tool from generic file siblings by the 'approved template' concept, though it does not explicitly name an alternative sibling.

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?

The phrase 'cho một loại tài liệu' gives clear context for when to use this tool: when an approved template file for a document type is needed. However, it provides no guidance about when to supply optional market/customer parameters and no explicit when-not-to-use or alternative-tool routing.

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

Deploy Server