Kintone Book Management MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KINTONE_APP_ID | Yes | Your Kintone application ID | |
| KINTONE_BASE_URL | Yes | Your Kintone base URL | |
| KINTONE_API_TOKEN | Yes | Your Kintone API token | |
| KINTONE_REQUEST_FIELDS | Yes | Your Kintone request fields |
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 |
|---|---|
| get-book-informationC | Get book information in the Information Systems Department |
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 single tool has a clear, distinct purpose of retrieving book information.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get-book-information), which is appropriate and consistent within this minimal set.
A single tool for a book management system is too few for the apparent scope, as it only supports retrieval without create, update, delete, or other management operations. This severely limits functionality and indicates an incomplete tool surface.
The tool set is severely incomplete for a book management domain. It only provides a get operation, lacking essential CRUD operations like create, update, and delete, as well as other expected features such as searching or listing books, which will cause agent failures in typical management workflows.