Skip to main content
Glama

kintone_get_form_fields

Retrieve field definitions, types, display names, and validation rules for a Kintone app using its app ID. Requires prior listing of apps to obtain the ID.

Instructions

⭐ ESSENTIAL: Get field definitions, types, display names, and validation rules for a Kintone app. ⚠️ Use 'kintone_list_apps' first to get available app IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesThe ID of the Kintone app (use kintone_list_apps to see available app IDs)

Implementation Reference

  • The handler function _handle_get_form_fields that executes the kintone_get_form_fields tool logic. It extracts app_id from arguments, calls client.get_form_fields(), and formats the response with field code, label, type, and required status.
    async def _handle_get_form_fields(arguments: Dict[str, Any], client: KintoneClient) -> List[types.TextContent]:
        """Handle kintone_get_form_fields tool call."""
        app_id = arguments.get("app_id")
    
        if not app_id:
            return [types.TextContent(
                type="text",
                text="Error: app_id is required"
            )]
    
        result = client.get_form_fields(app_id=app_id)
    
        if result.get("success"):
            properties = result.get("properties", {})
    
            response_text = f"Successfully retrieved form fields for app {app_id}\n\n"
    
            if properties:
                response_text += "Field Definitions:\n"
                for field_code, field_info in properties.items():
                    field_type = field_info.get("type", "N/A")
                    label = field_info.get("label", "N/A")
                    required = field_info.get("required", False)
    
                    response_text += f"- {field_code}: {label} ({field_type})"
                    if required:
                        response_text += " [Required]"
                    response_text += "\n"
    
                response_text += f"\nComplete Field Properties:\n{json.dumps(properties, indent=2, ensure_ascii=False)}"
            else:
                response_text += "No field definitions found."
    
            return [types.TextContent(
                type="text",
                text=response_text
            )]
        else:
            error_msg = result.get("error", "Unknown error occurred")
            return [types.TextContent(
                type="text",
                text=f"Error retrieving form fields for app {app_id}: {error_msg}"
            )]
  • The tool registration schema for kintone_get_form_fields, defining inputSchema with a required 'app_id' string parameter and a descriptive name/description.
    types.Tool(
        name="kintone_get_form_fields",
        description="⭐ ESSENTIAL: Get field definitions, types, display names, and validation rules for a Kintone app. ⚠️ Use 'kintone_list_apps' first to get available app IDs.",
        inputSchema={
            "type": "object",
            "properties": {
                "app_id": {
                    "type": "string",
                    "description": "The ID of the Kintone app (use kintone_list_apps to see available app IDs)"
                }
            },
            "required": ["app_id"]
        }
  • The routing in server.py where kintone_get_form_fields is matched in the metadata tools list and dispatched to handle_metadata_tools.
    # Metadata tools
    elif name in ["kintone_list_apps", "kintone_get_app", "kintone_get_form_fields",
                  "kintone_get_views", "kintone_get_form_layout"]:
        return await handle_metadata_tools(name, arguments, client)
  • The KintoneClient.get_form_fields() method that calls the Kintone REST API endpoint 'app/form/fields.json' with the app_id and returns field properties.
    def get_form_fields(self, app_id: str) -> Dict[str, Any]:
        """Get field definitions, types, display names, validation rules."""
        params = {'app': app_id}
    
        result = self._make_request('GET', 'app/form/fields.json', params=params)
    
        if result['success']:
            return {
                "success": True,
                "properties": result['data'].get('properties', {})
            }
        return result
Behavior3/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. It states the tool retrieves definitions but does not mention idempotency, safety, authentication needs, or rate limits. As a read operation, minimal behavioral disclosure is acceptable but could be improved.

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 sentences: first provides purpose, second gives usage hint. Every sentence adds value, no fluff. Well front-loaded.

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?

For a simple read tool with one parameter and no output schema, the description covers essential purpose and a usage prerequisite. Lacks behavioral context that annotations would provide, but is largely sufficient.

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 already includes the same prerequisite hint. The tool description adds no new parameter-specific details beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Description explicitly states 'Get field definitions, types, display names, and validation rules for a Kintone app.' It includes a specific verb and resource, and clearly distinguishes from sibling tools like kintone_get_app and kintone_get_form_layout.

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?

The description includes a clear prerequisite: 'Use 'kintone_list_apps' first to get available app IDs.' This guides the agent on proper usage. No explicit when-not-to-use or alternatives, but the guideline is valuable.

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/luvl/mcp-kintone-lite'

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