Nexxupp MCP Server

Official

by Nexxupp-Organization

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

nws_read_database

Read an NWS database schema and rows, optionally through a view, to inspect and retrieve data for analysis.

Instructions

Read an NWS database schema plus rows, 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_read_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.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It implies a read-only operation, but says nothing about permissions, whether rows are paginated or truncated, how large result sets are handled, or what the view path changes behaviorally.

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?

A single front-loaded sentence with no wasted words, though its brevity borders on under-specification given the tool's complexity.

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 2-parameter tool with no annotations and no output schema, the description is too thin: it doesn't clarify result scope (all rows vs. bounded), what a 'view' lookup returns, or the meaning of databaseId.

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 coverage is 0%, so the description must compensate. It only vaguely hints that viewId is optional ('optionally through a view') and says nothing about databaseId or the identifier format for either parameter.

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 gives a specific verb (Read) and resource (NWS database schema plus rows), and the 'optionally through a view' clause distinguishes it from write-oriented siblings like nws_upsert_rows. It does not explicitly name or contrast with a sibling such as nws_summarize_database, so it stops short of 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 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 nws_summarize_database, nws_search, or nws_upsert_rows, and no prerequisites or exclusions are stated. Usage is only implied by the verb 'Read'.

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