Single-tool server with a complex, domain-specific operation. The create_content_type tool has a comprehensive input schema with nested objects and detailed parameter descriptions. However, several critical quality issues reduce the overall score: (1) Tool name lacks clarity, 'create_content_type' is verb+noun but does not convey the complexity of required inputs (schema, field rules, taxonomies), forcing the LLM to read the full description; (2) Description is present (~200 chars) but lacks WHEN to use guidance or prerequisites (e.g., 'Must have Contentstack Management API access'); (3) Schema is deeply nested with type='any' for condition values, reducing validation strictness; (4) No documented output schema or error handling guidance visible in src/index.ts; (5) No per-request error handling showing LLMs how to self-correct invalid schemas or field definitions; (6) Tool marked as WRITE risk but no confirmation/dry-run pattern is evident; (7) Only one tool in the entire server limits composition assessment.

• Document the full output schema for create_content_type, specify which fields are returned (e.g., uid, created_at, updated_at, schema, options) and their types so LLMs can extract and use the created content type UID in follow-up operations.
• Replace type='any' in conditions[].value with a discriminated union or oneOf schema based on operator type, or add explicit validation in the implementation with clear error messages ('Invalid condition value for operator "equals", must be string, not array').
• Add explicit error recovery guidance to the description: 'If schema validation fails, the response will detail which field is invalid. Common issues: duplicate field UIDs, unsupported data_type values, or invalid field_metadata structure. Retry with corrected field definitions or call list_content_types to see examples.'
• Enhance the tool description to include: 'Creates a new content type schema that defines the structure for entries. Use this to set up a new content model with fields, validation rules, and taxonomy bindings before creating entries. Requires CONTENTSTACK_MANAGEMENT_TOKEN with write:content_type permissions.'
• Add an enumerate of valid operator values in the field_rules.conditions.operator parameter description (e.g., 'Operator for condition: must be one of equals, contains, matches, is_true, is_false').
• Implement a confirmation_required pattern or optional dry-run parameter ('dry_run: true would validate the schema and return validation errors without persisting it') to prevent accidental invalid content type creation.