Skip to main content
Glama
Sign In
Nativekeel

Nativekeel

by AlicanAkyol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

upgrade_plan

Read-onlyIdempotent

Generates an ordered upgrade plan for React Native or Expo apps, sequencing security fixes, crash risks, store deadlines, framework upgrades, and library replacements with reasons and concrete file-level steps.

Instructions

Ordered, step-by-step upgrade plan for a React Native or Expo project: phases in the order to do them (security fixes, crash risks, store deadlines, React Native and Expo upgrades, library replacements), the reason for each phase and concrete steps with file names. Use this once the decision to upgrade is made and the user wants the work in order; call upgrade_readiness first for the go/no-go. For non-upgrade priorities use improve_app. Built from the same scan as scan_project; stops with a warning if the project contains planted malware. Read-only.

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": {
      "path": "<path>"
    },
    "name": "upgrade_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFolder of the React Native or Expo app (the one with package.json), absolute or relative to the workspace. Must be inside the folders this server may read.
offlineNotrue: make no network requests (skip the npm and React Native Directory lookups behind version, maintenance and vulnerability checks). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds real behavioral context beyond them: it is built from the same scan as scan_project, and it aborts with a warning if planted malware is found. It does not describe output volume or how long the scan takes.

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?

Front-loaded with the deliverable, then usage routing, then provenance and the malware guard. Dense but each clause carries information; the trailing 'Read-only.' is redundant with annotations but minor.

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?

No output schema, but the description gives enough shape for the agent to set expectations (phases in order, reasons, concrete steps with file names) and discloses the malware abort condition. A brief note on plan length or scan cost would complete it.

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?

Schema description coverage is 100%, so both path and offline are fully documented in the schema; the description adds no syntax or format detail beyond that. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific deliverable (ordered, step-by-step upgrade plan) and enumerates the phase categories it produces, so the agent knows exactly what this tool returns versus a readiness verdict or a general improvement list.

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

Usage Guidelines5/5

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

Explicit sequencing: use this once the upgrade decision is made, call upgrade_readiness first for go/no-go, and use improve_app for non-upgrade priorities. Alternatives and their conditions are named directly.

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