Skip to main content
Glama

Create wiki

wiki_create

Create an organization-visible wiki; whoever creates it is its admin. Its pages start with its name and a colon (handbook:).

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": {
      "name": "<name>",
      "org": "<org>"
    },
    "name": "wiki_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization to create the wiki in. Required on every call, even when only one organization is listed; a path never names it.
nameYesA new wiki name. The name general is reserved.
titleNo
descriptionNoWhat belongs in the new wiki and what does not, in a sentence or two. Agents and people choose wikis by it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare write, non-open-world, non-destructive. The description goes beyond that by disclosing the visibility model (organization-visible) and the permission consequence (creator becomes admin), plus the page-namespacing convention, which is real behavioral context an agent could not infer from the annotations. It stops short of stating the return value or duplicate-name 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?

Two short sentences, no filler, with the visibility model front-loaded and the naming convention illustrated concretely in parentheses. Every clause carries information.

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

Completeness3/5

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

For a 4-parameter create tool with no output schema, an agent still lacks the return shape (what identifies the created wiki) and the failure mode on a duplicate or reserved name. Visibility, permissions, and naming are well covered, so the gap is narrow but real for a mutation.

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?

With 75% schema description coverage the schema already carries most parameter meaning, so 3 is the baseline. The description does add one genuinely non-obvious fact — that pages are prefixed with the wiki name and a colon, exampled as handbook: — which clarifies the naming semantics of the name parameter, but it says nothing about org, title, or description.

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?

States a specific verb and resource ("Create an ... wiki") and adds the defining scope: organization-visible, creator is admin. That is enough for an agent to separate it from site_create or code_create without opening a schema, though it never names a sibling explicitly.

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?

Usage is only implied by the verb — create a new wiki when none exists. There is no statement of prerequisites, no advice to check wiki_list/wiki_get first, and no mention of what happens when the name already exists. The visibility and admin notes are context, not when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources