Nexxupp MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

nws_summarize_database

Summarize an NWS database's contents, optionally through a view, so AI agents can understand stored data and structure without manual review.

Instructions

Summarize an NWS database's contents, optionally through a view.

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": {
      "databaseId": "<databaseId>"
    },
    "name": "nws_summarize_database"
  }
}

Input Schema

Name	Required	Description	Default
`viewId`	No
`databaseId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

C2.8/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 burden of behavioral disclosure. 'Summarize' implies a read-only operation, but the description does not confirm read-only safety, mention side effects, auth requirements, or any output characteristics.

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?

A single, front-loaded sentence with no wasted words. The purpose and optional parameter are stated efficiently.

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 tool with no annotations, no output schema, and 0% parameter coverage, the description leaves significant gaps: it does not explain when to choose this over siblings, what the summary contains, or any behavioral constraints. Given the dense sibling list, an agent lacks enough context to invoke confidently.

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%, so the description must compensate. It only adds meaning for viewId ('optionally through a view') and implicitly for databaseId ('database's contents'); neither parameter receives explicit format, validity, or required/optional detail beyond what the names already convey.

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?

States a specific verb (Sumarize) and resource (NWS database's contents), and adds an optional scope (through a view). Clear enough to distinguish from nws_read_database, but it does not explicitly name or contrast any sibling tool.

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?

No guidance on when to use this tool versus alternatives like nws_read_database or nws_summarize_station. The only contextual hint is 'optionally through a view', which describes a parameter, not a usage condition.

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