kintone MCP Server

Official

by kintone

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Remote

Get App

kintone-get-app

Retrieve app settings from kintone by providing an app ID. Get configuration details for a specific kintone app.

Instructions

Get app settings from kintone

Input Schema

TableJSON Schema

Name	Required	Description	Default
`appId`	Yes	The ID of the app to retrieve (numeric value as string)

Output Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	The app code (empty string if not set)
`name`	Yes	The app name
`appId`	Yes	The app ID
`creator`	Yes	The creator information
`spaceId`	Yes	The space ID (null if not in a space)
`modifier`	Yes	The modifier information
`threadId`	Yes	The thread ID (null if not in a space)
`createdAt`	Yes	The creation date and time
`modifiedAt`	Yes	The last modified date and time
`description`	Yes	The app description (empty string if not set)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.9.3Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / spaceId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / threadId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Addedv1.9.1Jul 24, 2026
Removedv1.9.0Jul 22, 2026
First observedv1.4.0May 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not mention authentication requirements, error behavior, or what happens when the app does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler or redundant content. It is appropriately short for a simple one-parameter read operation, though it sacrifices useful context for brevity.

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?

A simple tool with one documented parameter and an output schema is largely callable as-is. However, the description is incomplete for tool selection because it does not clarify the relationship to kintone-get-general-settings or other getter siblings.

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%, and the single parameter appId is already well documented in the input schema. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Get') and a resource ('app settings'), but 'app settings' is vague in the context of siblings like kintone-get-general-settings. An agent cannot tell whether this returns general settings only or broader app configuration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool over kintone-get-general-settings or the other getter siblings. There are no exclusions, alternatives, or contextual triggers provided.

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