Skip to main content
Glama

Create collection section

create_collection_section
Idempotent

Creates a named section within an existing collection. Use sections to organize collection content into groups, such as topics or chapters. Returns the section ID to pass to add_collection_content.

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": {
      "idempotency_key": "<idempotency_key>",
      "collection_id": "<collection_id>",
      "expected_revision": "<expected_revision>",
      "name": "<name>"
    },
    "name": "create_collection_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
collection_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the parent collection must already exist and that an ID is returned for chaining, but it says nothing about how the required idempotency_key affects repeated calls or how expected_revision conflicts surface, both of which are non-obvious for a mutating tool.

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?

Three short sentences with zero waste: purpose first, usage context second, return/next-step last. Every sentence earns its place.

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 mutation tool with four required, entirely undocumented parameters and no output schema, the description leaves major gaps: idempotency semantics, optimistic-concurrency behavior of expected_revision, and error modes. It covers the happy path and chaining but not enough for an agent to call it correctly under retry or conflict conditions.

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

Parameters2/5

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

Schema description coverage is 0% for four required parameters, so the description must compensate and largely does not. It implicitly covers name and collection_id ('named section within an existing collection'), but idempotency_key and expected_revision — the two parameters an agent is most likely to get wrong — are never explained.

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 named section inside an existing collection, making it clearly distinct from create_collection (which makes the collection itself). It stops short of naming a sibling explicitly, so it is clear but not maximally differentiating.

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?

It gives a concrete use case ('organize collection content into groups, such as topics or chapters') and states the follow-on step by naming add_collection_content as the consumer of the returned section ID. There is no when-not-to-use guidance or note on what happens if the section name already exists.

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