COBie MCP

Overview Schema Source Related Servers Discussions Admin

validate_document_input

Validates document input by checking the target row exists and that category, approvalBy, and stage values are in their respective picklists. Returns validation errors or success.

Instructions

Validate Document input before creation (proactive check).

Checks:
- Target entity (SheetName + RowName) exists
- Category exists in PickList.DocumentType
- ApprovalBy exists in PickList.ApprovalBy
- Stage exists in PickList.StageType

Returns validation result with errors or success message.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`stage`	No
`category`	No
`row_name`	Yes
`excel_path`	Yes
`sheet_name`	Yes
`approval_by`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 7, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden. It discloses that the tool returns a validation result with errors or success, but does not state whether it modifies data, required permissions, or failure behavior.

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?

The bullet-list format is compact and scannable; every sentence adds relevant information without redundancy.

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?

Covers what the validation checks and the general return type, but omits the exact output schema/format and does not specify behavior when optional fields are omitted.

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?

No per-parameter descriptions are provided in the schema. The description explains checks for sheet_name, row_name, category, approval_by, and stage, but leaves excel_path and optional/nullable semantics unexplained.

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?

Clearly states the tool validates document input before creation and lists exact checks, differentiating it from validation of COBie or draft results and from document creation tools.

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?

Indicates it is a proactive pre-creation check, implying use before document creation; however, it does not explicitly contrast with sibling validation tools or state when not to use it.

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

Deploy Server