Skip to main content
Glama
Sign In
Nexxupp MCP Server

Nexxupp MCP Server

Official
by Nexxupp-Organization
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

nws_apply_template_blocks

Appends template blocks to an NWS page, enabling structured content assembly by adding blocks with specified types and sort order.

Instructions

Append template blocks to an NWS page.

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": {
      "pageId": "<pageId>",
      "blocks": "<blocks>"
    },
    "name": "nws_apply_template_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYes
pageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Append' usefully implies existing content is preserved rather than replaced, but the description says nothing about required permissions, ordering/conflict behavior, atomicity, or what is returned after the write.

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 single sentence is front-loaded and waste-free, but at six words it is under-specified rather than concise for a tool with a nested, undocumented block payload. Brevity here reflects missing information, not economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, 0% parameter coverage, and a nested array of loosely typed block objects, the description omits everything an agent needs to invoke this tool correctly. It is not complete for the complexity involved.

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

Parameters1/5

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

Schema description coverage is 0% across two parameters, and the 'blocks' parameter is a structured array whose items require 'block_type' and 'sort_order' while leaving 'props', 'content', and 'parent_id' completely untyped. The description adds no meaning for pageId or for any block field, so it fails to compensate for the schema gap.

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 pairs a specific verb ('Append') with a concrete resource ('template blocks') and target ('an NWS page'), so an agent knows this is an additive write to a page. It does not explicitly distinguish itself from sibling tools like nws_search_blocks or nws_open_page_for_event, but the action is unambiguous.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g. must the page exist or be open first?), and no exclusions. The one sentence gives no routing guidance at all.

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

Deploy Server

Other Tools