Skip to main content
Glama
Lex6won
by Lex6won

render_report

Converts scan results into a self-contained Korean report in Markdown, HTML, or both, suitable for sharing with non-technical stakeholders or attaching to approval records.

Instructions

ScanReport(scan_code / scan_path 결과)를 한국어 보고서로 렌더링합니다.

사람이 읽고 결재·보고에 쓸 문서가 필요할 때 사용하세요.

  • format="markdown": Markdown 본문(기본)

  • format="html": 자체 포함 단일 HTML(외부 CDN·JS 없음, 인쇄→PDF·이메일 가능)

  • format="both": Markdown + HTML 모두

출력은 자체 완결적이라 비전공 이해관계자 공유나 내부 승인 기록 첨부에 적합합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportYes
formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the self-contained output and format differences, but lacks details on error cases or state changes.

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 concise sentences plus a bullet list efficiently convey purpose, usage, and format options without redundancy.

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?

Given the output schema exists, the description adequately covers input transformation and format, though it could clarify how the output is delivered.

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?

The description explains the format parameter thoroughly but only notes the report parameter is a ScanReport object without detailing its structure, despite 0% schema coverage.

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 renders ScanReport results into a Korean report, distinguishing it from scanning and checking sibling tools.

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?

It explicitly says to use when a human-readable report for approval/sharing is needed, but does not mention when not to use or provide alternatives.

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/Lex6won/vibecode-checker'

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