Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-CreateContainer

Creates a LinkedDataHub container document at a URL relative to a parent container, enforcing trailing slashes and optional idempotent behavior for existing URIs.

Instructions

Creates a LinkedDataHub Container document with proper structure.

    IMPORTANT CONSTRAINTS:
    - The document URL needs to end with a trailing slash (/)
    - Documents can only be created at URLs relative to existing container's URL
    - Example: if https://localhost/blog/ exists, you cannot create https://localhost/blog/posts/something/
      before creating https://localhost/blog/posts/ 
    - LinkedDataHub automatically manages timestamps (dct:created, dct:modified)
    - LinkedDataHub automatically manages parent-child relationships (sioc:has_parent) based on URI hierarchy
    - It only creates: a document already at the URI is left as it is and the operation fails, unless
      if_absent is true, which accepts it as the result (like mkdir -p). To replace a document, PUT it.

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": {
      "parent": "<parent>",
      "title": "<title>"
    },
    "name": "ldh-CreateContainer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL path segment (optional). Defaults to a random UUID.
titleYesThe title of the container
parentYesURI of the parent container
if_absentNoOptional: whether a document already at the URI counts as success, left as it is (like mkdir -p). Without it the operation fails there.
descriptionNoDescription (optional)
children_viewNoOptional: whether the container's first content block lists its children (the shared ldh:ChildrenView). It does unless this is false; the content is then added with ldh-AddObjectBlock and ldh-AddXHTMLBlock, as to any document.
primary_topicNoURI reference of what the container is about, resolved against its URI (optional), e.g. #this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well. It discloses automatic timestamp and parent-child management, failure behavior when a document already exists, the if_absent alternative, and the fact that replacement must go through PUT.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and then organized under an 'IMPORTANT CONSTRAINTS' heading. There is some repetition between the main text and the if_absent schema description, but the wording is generally efficient and actionable.

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?

For a seven-parameter creation tool with no annotations and no output schema, the description covers the important structural constraints and failure behavior thoroughly. It does not describe the return value or how description, children_view, and primary_topic affect the resulting document, but the schema already documents those fields.

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?

Schema description coverage is already 100%, so the baseline would be 3. The description adds useful meaning for key parameters by explaining the trailing-slash URL constraint, relative parent placement, and the mkdir -p-like semantics of if_absent.

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 states a specific verb and resource: it 'Creates a LinkedDataHub Container document with proper structure.' It distinguishes this from replacement by explicitly directing agents to PUT for that case, though it does not directly contrast with sibling creation tools such as ldh-CreateItem.

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?

The description gives concrete usage constraints, including the trailing-slash requirement, relative URL placement, and parent-container prerequisite. It also names an alternative for replacement ('To replace a document, PUT it') and explains the if_absent branch, but does not discuss when a different creation tool should be preferred.

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