Iris MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_release_noteB | タグ間の差分からリリースノートを生成します |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined as generating release notes from tag differences, making it impossible for an agent to confuse it with another tool.
Since there is only a single tool, naming consistency is inherently perfect. The tool name 'generate_release_note' follows a clear verb_noun pattern, and there are no other tools to create inconsistency with.
A single tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or overly narrow scope. This makes the server feel thin and impractical for most agent workflows, as it lacks the breadth needed for typical operations in its domain.
The server is severely incomplete for any reasonable domain involving release notes. While the tool can generate notes, there are obvious gaps such as creating, updating, deleting, or listing release notes, and no coverage for related operations like managing tags or integrating with version control systems, which will cause agent failures in real-world scenarios.