Skip to main content
Glama

Add a new portal

add_new_portal_to_account
Destructive

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_new_portal_to_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the portal
slugNoSlug for the portal to display in link
colorNoHeader color for help-center
configNoConfiguration about supporting locales
archivedNoStatus to check if portal is live
page_titleNoPage title for the portal
header_textNoHelp center header
custom_domainNoCustom domain to display help center.
homepage_linkNolink to main dashboard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the risky profile is covered structurally. The description's one real contribution is the help_center feature gate; it does not explain what a partially-specified portal defaults to or that the operation is not repeatable.

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

Conciseness3/5

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

It is short, but the first two clauses restate each other ("Add a new portal. Add a new portal to account"), which is wasted text in a two-sentence description. The feature requirement, the most actionable element, is buried at the end.

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 nine-parameter, non-idempotent, destructive create with a nested config object and zero required fields, the description says almost nothing about outcome or defaults. An agent gets no indication of what happens if only `name` is supplied, or that repeated calls produce duplicate portals.

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% and every one of the nine properties carries its own description (name, slug, color, config, custom_domain, etc.), so the schema does the heavy lifting. The description adds no meaning about requiredness, defaults, or how the nested config object should be formed.

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?

"Add a new portal to account" gives a specific verb (add) and resource (portal) scoped to an account, which is enough to distinguish it from delete_portal and update_portal. It stops short of explicitly naming those siblings or the boundary between them, so it falls short of 5.

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?

The only guidance offered is a hard prerequisite: "Requires feature: help_center." That is genuinely useful gating information, but there is no statement of when to create a portal versus updating or deleting one, and no note that calling this twice creates two portals (non-idempotent).

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