Skip to main content
Glama

Add a new category

add_new_category_to_account
Destructive

Add a new category. Add a new category to portal Requires feature: help_center.

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": {
      "portal_id": "<portal_id>"
    },
    "name": "add_new_category_to_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCategory name
slugNoCategory slug
localeNoCategory locale
positionNoCategory position in the portal list to sort
portal_idYesThe slug of the portal, as it appears in its help center link (the parameter keeps its historical name)
descriptionNoCategory description
parent_category_idNoTo define parent category, e.g product documentation has multiple level features in sales category or in engineering category.
associated_category_idNoTo associate similar categories to each other, e.g same category of product documentation in different languages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the agent knows this is a non-idempotent write. The description's only added behavioral value is the `help_center` feature entitlement requirement, which is genuine context, but it never explains what the destructive flag means here or what happens on duplicate name/slug.

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

Conciseness2/5

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

The description is short but structurally wasteful: sentence one and sentence two both say "Add a new category," and the second is truncated mid-thought ("Add a new category to portal **Requires feature:**..."). The duplicated lead-in should have been replaced by the feature requirement and a scope 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 an eight-parameter mutation tool with no output schema, the description says nothing about the required portal_id, the parent/associated category relationships, or what is returned. The feature-flag note is the only operationally necessary piece it supplies, leaving the rest to the schema.

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%, including the useful clarification that portal_id holds a portal slug rather than an ID, so the schema already carries parameter meaning. The description adds nothing about the eight fields, which is acceptable at full coverage but is the baseline rather than an improvement.

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

Purpose3/5

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

The description names a specific verb and resource (add / category) and adds a scope hint ("to portal"), which separates it from delete_category and update_category by verb alone. However, the opening sentence is a tautological restatement of the title and the second sentence only repeats it with a prepositional phrase, so no real differentiating detail is supplied.

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 on when to use this versus update_category, delete_category, or add_new_portal_to_account, and no prerequisites beyond an implicit feature flag. The agent must infer the create-only context from the tool name.

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