Skip to main content
Glama

generate_usecase_specification

Generates a detailed use case specification in Vietnamese format with main, alternative, and exception flows, rendered as a markdown table with Actor/System columns. Optionally saves to a .md file.

Instructions

Generate a detailed use case specification (đặc tả use case) in Vietnamese format. Produces a structured document with use case name, actors, pre/post conditions, main flow, alternative flows, and exception flows — rendered as a markdown table with Actor/System columns. Optionally saves to a .md file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
triggerNoĐiều kiện kích hoạt use case
mainFlowYesLuồng sự kiện chính (happy case)
priorityNoMức độ ưu tiên (e.g., "Must Have", "Should Have")
useCaseIdNoMã định danh use case (e.g., "UC-01")
outputPathNoĐường dẫn file để lưu (optional)
descriptionYesMô tả sơ lược về use case
useCaseNameYesTên use case (e.g., "Đăng ký học phần")
outputFormatNoĐịnh dạng outputmarkdown
primaryActorYesActor chính
businessRulesNoCác quy tắc business (nếu có)
preConditionsYesDanh sách tiền điều kiện
exceptionFlowsNoCác luồng sự kiện ngoại lệ
postConditionsYesDanh sách hậu điều kiện
secondaryActorNoActor phụ (nếu có)
alternativeFlowsNoCác luồng sự kiện thay thế
nonFunctionalRequirementsNoYêu cầu phi chức năng (nếu có)
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses optional file saving and output format, but lacks details on file overwrite behavior, permissions needed, or other side effects. Basic transparency but incomplete for a mutation tool.

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?

Three sentences, front-loaded with purpose, then output format, then optional saving. No wasted words, efficient communication.

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?

The tool has 16 parameters and no output schema. The description explains the output structure but does not specify what the tool returns (e.g., markdown string) if no outputPath is given. Missing return behavior for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema documents all parameters. The description adds context by summarizing the document structure, but does not add meaning beyond the schema for individual parameters. Adequate but not exceptional.

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?

The description clearly states the tool generates a detailed use case specification in Vietnamese format, specifying the output as a structured markdown table. It distinguishes from sibling diagram tools by focusing on specification documents rather than visual diagrams.

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 description implies this tool is for generating use case specs, but it does not explicitly state when to use it versus alternatives (e.g., diagram tools) or provide exclusions. Context from sibling tool names helps, but no direct guidance is offered.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rifujin123/drawio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server