Skip to main content
Glama
vedangps

NitroStack Hackathon Starter

by vedangps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

NitroStack × Amrita Hackathon Starter

A verified, event-ready base for building a TypeScript MCP server with the official NitroStack SDK. The included calculator module is a working reference, not the final hackathon idea.

Live deployment

The service runs MCP protocol 2025-06-18. A live smoke test initializes the server, lists both tools, and executes 5 + 3 = 8.

Related MCP server: NitroStack Calculator MCP Server

Ready on this laptop

  • Node.js 20.18.1 and npm 10.8.2

  • Git and GitHub CLI

  • VS Code

  • NitroStudio 1.4.14

  • Official NitroStack CLI 1.0.15 installed globally

  • Official typescript-starter template

  • Root and widget dependencies installed

  • Local build, preflight checks, and GitHub Actions CI

  • Idea, build, security, submission, and three-minute demo templates

Start here

  1. Complete the short account checklist.

  2. Fill in the one-page idea brief with your team.

  3. Replace the calculator example with the smallest end-to-end version of your chosen idea.

  4. Run:

    npm run dev

  5. In NitroStudio, choose Add Server → Nitro Project, select this folder, and open Studio App Canvas.

Before every push:

npm run check

Project map

src/
├── index.ts
├── app.module.ts
├── health/
├── modules/
│   └── calculator/        # Replace with your MVP module
└── widgets/
    └── app/
docs/
├── IDEA.md
├── BUILD_PLAN.md
├── MANUAL_ACCOUNT_STEPS.md
├── PIZZA_REFERENCE_WORKFLOW.md
├── SUBMISSION_CHECKLIST.md
└── DEMO_SCRIPT.md
scripts/
└── preflight.mjs

Commands

Command

Purpose

npm run dev

Start the MCP server and widget dev server

npm run build

Build the production bundle

npm run check

Build, exercise the MCP server, and run preflight checks

npm run smoke:mcp

List and call MCP primitives through STDIO

npm run audit:all

Audit server and widget dependency trees

npm run start:prod

Run the built production server

npm run upgrade

Upgrade NitroStack packages

Non-negotiable event rules

  • Use the official NitroStack TypeScript SDK throughout the project.

  • Align the idea with an organizer-approved track.

  • Keep main working and deployable.

  • Deploy early to NitroCloud and test the live service after major changes.

  • Never commit .env, API keys, tokens, passwords, credentials, private keys, node_modules, or large binaries.

  • Keep the repository public through judging.

  • Submit the live NitroCloud deployment, complete GitHub repository, and a demo video no longer than three minutes through the organizer-provided account.

See SUBMISSION_CHECKLIST.md for the full gate.

Official links

Available Tools

2 tools
calculateC

Perform basic arithmetic calculations

ParametersJSON Schema
NameRequiredDescriptionDefault
aYesFirst number
bYesSecond number
operationYesThe operation to perform

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, so the description bears full responsibility. It states it performs calculations but omits potential side effects like division-by-zero errors or whether the tool is read-only, leaving behavior ambiguous.

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?

The description is extremely concise, using only four words to convey the entire purpose. There is no redundancy or unnecessary elaboration.

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?

The description lacks essential context such as the return format, error handling, or precision of results. Given no output schema and no annotations, the tool is incomplete for an agent to fully understand behavior without additional inference.

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 schema descriptions cover all parameters, giving a baseline of 3. The tool description itself adds no extra meaning beyond the schema, but the schema already defines 'a', 'b', and 'operation' sufficiently for basic arithmetic.

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 clearly states the tool performs basic arithmetic calculations, which is a specific action. It distinguishes itself from sibling tools like convert_temperature by being generic, though it lacks detail on exact operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as convert_temperature. There is no mention of typical use cases or conditions for selection.

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

convert_temperatureC

Convert temperature units based on file content or direct input. Supports Celsius (C) and Fahrenheit (F).

ParametersJSON Schema
NameRequiredDescriptionDefault
valueNoTemperature value to convert
to_unitNoUnit to convert to (C or F)
file_nameYesName of the uploaded file
file_typeYesMIME type of the uploaded file
from_unitNoUnit to convert from (C or F)
file_contentYesBase64 encoded file content. Will be injected by system.

TDQS

C2.7/5.0
Behavior1/5

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

The description states the tool works 'based on file content or direct input', but the schema requires file_name, file_type, and file_content for all invocations, making direct input impossible without dummy file data. This contradiction is misleading and fails to disclose the actual required behavior.

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 description is a single, short sentence that gets to the point quickly. It could be slightly more explicit about the file/direct input behavior, but overall it is concise and well-structured.

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?

The description lacks necessary context about the relationship between the file parameters and the temperature conversion parameters, especially given the required fields. There is also no explanation of output format or behavior when both file and direct input are provided, leaving the tool's usage incomplete.

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?

All parameters have descriptions, so schema coverage is complete, meeting the baseline. However, the descriptions are minimal, and the file-related parameters are confusing because they are marked required even for 'direct input' and provide no clarity on their purpose or interaction with the value/from_unit/to_unit parameters.

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 clearly states the tool converts temperature units between Celsius and Fahrenheit, identifying the specific verb and resource. However, the mention of 'file content or direct input' introduces some ambiguity about the exact mode of operation, slightly detracting from full clarity.

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 is provided on when to use this tool versus the sibling tools like 'calculate' or 'upload-and-analyze'. The description only explains what the tool does, not the scenarios in which it should be preferred.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedcalculate
    • First observedconvert_temperature
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one handles general arithmetic and the other handles temperature conversion. There is no overlap or ambiguity between them, so an agent can easily select the correct tool.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'calculate' and 'convert_temperature'. Both use lowercase with underscores, maintaining a predictable naming convention across the set.

Tool Count3/5

With only two tools, the server feels very thin for a 'Hackathon Starter' name, which suggests a broader utility toolkit. This makes the count borderline, though it is still functional for basic needs.

Completeness2/5

The server appears to aim at providing math utilities, but it only offers basic arithmetic and temperature conversion. There are significant gaps such as length/weight conversions, currency conversion, or more advanced math functions, leaving the surface severely incomplete for a general-purpose starter kit.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • NitroStack Calculator MCP

    VRDhwaraganath
    F
    license
    B
    quality
    C
    maintenance
    A minimal MCP server template for learning NitroStack fundamentals, featuring a calculator module with tools, resources, and prompts.
    6
    -

  • NitroStack Calculator MCP

    Tarika06
    F
    license
    C
    quality
    C
    maintenance
    A minimal MCP server template for learning NitroStack fundamentals, featuring a calculator module with tools, resources, and prompts.
    9
    -

  • NitroStack Starter Template

    projectakshith
    A
    license
    Not graded
    quality
    C
    maintenance
    This template enables learning NitroStack fundamentals with a calculator-focused MCP server that supports tools, resources, and prompts. It includes TypeScript and Zod validation for building MCP servers.
    205 npm
    1
    MIT