Dedox

Create article

create_article

Create a new article in a knowledge base

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "knowledgeBaseId": "<knowledgeBaseId>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_article"
  }
}

Input Schema

Name	Required	Description
`seo`	No	SEO metadata object with optional fields: metaTitle (max 60 chars), metaDescription (max 160 chars), keywords (array of strings or comma-separated string)
`slug`	No	URL slug (auto-generated from title if not provided)
`tags`	No	Array of tag strings
`title`	Yes	Article title
`status`	No	Article status (default: draft)
`content`	Yes	Article content (Markdown format, will be converted to HTML)
`excerpt`	No	Short description or excerpt (max 500 characters)
`category`	No	Article category
`knowledgeBaseId`	Yes	Knowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description adds almost nothing beyond the purpose statement—it does not disclose required permissions, duplicate-creation behavior, status defaults, or what happens to the content conversion.

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 is a single front-loaded sentence with no wasted words. It is appropriately sized for a short purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation tool with a nested object and no output schema, the description is too sparse. It omits required-field expectations, status behavior, content conversion, slug auto-generation, and any return-value context, leaving the schema and annotations to carry nearly all the burden.

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%, so every parameter is already documented in the input schema. The description itself adds no parameter-specific information, so the baseline of 3 is appropriate.

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 a specific verb and resource: creating a new article in a knowledge base. It does not, however, differentiate this from sibling tools like update_article or create_knowledge_base, though the name itself makes the operation fairly clear.

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?

There is no guidance about when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent must infer that this is for article creation and not for updating or restoring versions.

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

All Dedox tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?