form-auto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | No | API key for Google Sheets access (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-workflowA | 엑셀 또는 Google Sheets 데이터를 읽어 내부 시스템 폼을 자동으로 입력합니다. 엑셀에 메뉴경로, 폼 필드, 저장버튼 텍스트가 모두 포함되어 있습니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined as running a data-driven form workflow, so an agent can accurately select it without ambiguity.
The tool name 'run-workflow' follows a clean verb-noun pattern, which is consistent and readable. Since there is only one tool, no naming conflicts or stylistic inconsistencies exist.
A single tool feels thin for the stated purpose of form automation, which could encompass a broader set of operations. The count is borderline but not extreme, as the tool covers the core workflow directly.
The tool addresses the primary task of reading data and filling forms, but there are notable gaps such as listing workflows, checking status, or handling configuration. For a more comprehensive form automation server, additional tools would be expected.