Skip to main content
Glama

Get Magic Content Settings

get_magic_content_settings
Read-only

Get Magic Content generation settings for a community. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>"
    },
    "name": "get_magic_content_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoDecision on the customer request; use one of the allowed values.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
videoProviderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Decision on the customer request; use one of the allowed values."
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this as a read-only, non-destructive, closed-world call, so the description's job is to add context — and it does: FREE businesses are excluded regardless of individual feature rows, a grace-period warning and verified resubscribe link must be shown. That is meaningful authorization/eligibility behavior an agent would not otherwise know. It does not describe rate limits or error shapes, so not a 5.

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 purpose is front-loaded in the first sentence, followed by gating rules in priority order. There is mild redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs', which repeats the same instruction twice, costing it a 5.

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 three-parameter read of settings, the description covers the hardest part — the entitlement gate — thoroughly. With no output schema, it gives no indication of what settings are returned, and videoProvider's role is undocumented, but these are modest gaps for a straightforward getter.

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?

The description never mentions communityId, action, or videoProvider. Schema coverage is 67%, with 'action' and 'communityId' well documented in-schema and 'videoProvider' left entirely unexplained in both places. That lands at the baseline 3 — the schema carries most of the load, with one parameter undocumented everywhere.

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 first sentence names a specific verb+resource pair ('Get Magic Content generation settings') and scopes it to 'a community', which is clear enough to distinguish it from siblings like get_magic_content or list_magic_content_styles. It does not explicitly contrast itself with those siblings, keeping it below a 5.

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?

Strong precondition guidance: check business permissions before offering the action, call check_business_tool_access before collecting inputs, never proceed when access is blocked. This tells the agent exactly what must happen first. It stops short of 5 because there is no guidance distinguishing this getter from other Magic Content read tools (get_magic_content, list_magic_content_styles) once access is confirmed.

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