Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-CreateItem

Creates a structured LinkedDataHub Item document under an existing container, requiring a title and valid trailing-slash URL with optional slug, description, and topic.

Instructions

Creates a LinkedDataHub Item 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": {
      "container": "<container>",
      "title": "<title>"
    },
    "name": "ldh-CreateItem"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL path segment (optional). Defaults to a random UUID.
titleYesThe title of the item
containerYesURI 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)
primary_topicNoURI reference of what the item 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.3/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 burden and does so well: it discloses auto-managed fields (dct:created, dct:modified, sioc:has_parent), the failure semantics when a document already exists, and how if_absent changes that to mkdir -p behavior. This is exactly the non-obvious side-effect information an agent needs before a write.

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?

Front-loads the purpose sentence, then a bulleted constraints block that is easy to scan. The worked example about https://localhost/blog/posts/ partly restates the preceding bullet, so there is minor redundancy, but every constraint 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?

For a six-parameter write tool with no annotations and no output schema, the description covers preconditions, side effects, and failure modes thoroughly. It stops short of saying what the tool returns on success (e.g. the created document URI) or any permission requirements.

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 the baseline is 3. The description reinforces if_absent semantics and the container/slug relationship via the hierarchy example, but adds no new meaning beyond the schema's own parameter descriptions.

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

Purpose5/5

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

States a specific verb and resource ('Creates a LinkedDataHub Item document') and scopes it to Item documents, which implicitly separates it from ldh-CreateContainer and the raw PUT/Replace siblings. The note 'To replace a document, PUT it' further sharpens what this tool is not for.

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?

Gives concrete preconditions (trailing slash required, parent container must already exist) with a worked example, and names the replacement alternative (PUT). It does not explicitly contrast with ldh-CreateContainer, so the choice between the two creation tools is left partly to inference.

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