Skip to main content
Glama

contentrain_describe_format

Get the Contentrain content file format specification including JSON structure, markdown conventions, meta files, and locale strategies for any language or platform.

Instructions

Describes the Contentrain content file format for any language/platform. Returns a comprehensive specification of the file structure, JSON formats, markdown conventions, meta files, and locale strategies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the contentrain_describe_format tool, which returns a documentation object describing the Contentrain file system structure and data formats.
    server.tool(
      'contentrain_describe_format',
      'Describes the Contentrain content file format for any language/platform. Returns a comprehensive specification of the file structure, JSON formats, markdown conventions, meta files, and locale strategies.',
      {},
      async () => {
        const formatSpec = {
          overview: 'Contentrain stores content as plain JSON and Markdown files in a .contentrain/ directory at the project root. All files are committed to git.',
          directory_structure: {
            description: 'Standard layout of .contentrain/ directory',
            layout: {
              '.contentrain/config.json': 'Project configuration (stack, workflow, locales, domains)',
              '.contentrain/context.json': 'Last operation metadata (written by MCP after every write)',
              '.contentrain/vocabulary.json': 'Shared vocabulary/terms (optional)',
              '.contentrain/models/{model-id}.json': 'Model schema definitions',
              '.contentrain/content/{domain}/{model-id}/': 'Content files per model',
              '.contentrain/meta/{model-id}/': 'Metadata files per model (status, source, timestamps)',
            },
          },
          model_kinds: {
            collection: {
              description: 'Multiple entries stored as an object-map keyed by entry ID',
              storage_format: 'JSON object-map: { "entry-id-1": { ...fields }, "entry-id-2": { ...fields } }',
              note: 'Keys are sorted alphabetically for canonical output. Entry IDs are alphanumeric (1-40 chars, hyphens/underscores allowed).',
              example: '{ "abc123": { "title": "Hello", "slug": "hello" }, "def456": { "title": "World", "slug": "world" } }',
            },
            singleton: {
              description: 'Single entry (e.g. site settings, hero section)',
              storage_format: 'JSON object with field key-value pairs: { "title": "My Site", "description": "..." }',
            },
            document: {
              description: 'Markdown files with YAML-like frontmatter',
              storage_format: 'Markdown file: ---\\nslug: my-post\\ntitle: My Post\\n---\\n\\nMarkdown body content here.',
              frontmatter_rules: [
                'Delimited by --- on its own line',
                'Key-value pairs: key: value',
                'Arrays: key:\\n  - item1\\n  - item2',
                'Inline arrays: key: [item1, item2]',
                'Values auto-parsed: true/false -> boolean, integers -> number, quoted -> string',
                '"body" key is reserved for the markdown content below the frontmatter',
              ],
            },
            dictionary: {
              description: 'Flat key-value string map (e.g. i18n translation files)',
              storage_format: 'JSON object: { "greeting": "Hello", "farewell": "Goodbye" }',
              note: 'All values must be strings.',
            },
          },
          meta_files: {
            description: 'Metadata is stored separately from content in .contentrain/meta/{model-id}/',
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully describes the return value ('comprehensive specification' covering file structure, meta files, and locale strategies), but omits safety characteristics (e.g., read-only status) or performance considerations.

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 description consists of two efficient sentences with zero waste: the first defines the action and scope, while the second details the return value. Information is front-loaded and every sentence earns its place.

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?

Given the absence of input parameters, annotations, and output schema, the description adequately covers the essential information—what the tool does and what comprehensive details it returns (file structure, conventions, strategies). Sufficient for a simple documentation retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, establishing a baseline score of 4. The description does not need to compensate for parameter documentation, and appropriately focuses on the tool's behavior and output rather than non-existent inputs.

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

Purpose4/5

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

The description clearly states the tool 'Describes the Contentrain content file format' with specific scope ('any language/platform'), providing a concrete verb and resource. However, it does not explicitly differentiate from the sibling tool 'contentrain_describe', leaving potential ambiguity about which description tool to use.

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

Usage Guidelines3/5

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

The description implies usage context—invoking this when needing to understand file structure, JSON formats, and markdown conventions—but lacks explicit 'when to use' or 'when not to use' guidance relative to alternatives like 'contentrain_describe'.

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/Contentrain/ai'

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