Skip to main content
Glama

Confirm app framework

setFramework
Idempotent

Confirm the app type (framework preset) Tofu detected, before the first deploy — and before the app’s database is connected, since the browser-facing key names come from the preset recorded then. static is an already-built site (root index.html, no build step); a server preset (fastapi, flask, django, python, go, express, hono, nestjs, node) runs the app as an HTTP process that listens on PORT and answers /; container builds the app’s own container file at its root — selecting container for a bare root Dockerfile makes that image the deployment source. A preset the upload does not fit is refused with the rule and the fix.

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": {
      "projectId": "<projectId>",
      "framework": "<framework>"
    },
    "name": "setFramework"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, idempotent, non-destructive call; the description adds real behavior beyond that: a mismatched preset is refused with the rule and the fix, and selecting `container` makes the root container image the deployment source. It does not describe the success response or re-confirmation semantics, but the key side effects are disclosed.

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 action and timing, then the enum semantics, then the refusal behavior — every sentence carries information. The single long paragraph is dense rather than wasteful, though a list form would scan better.

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?

For a two-parameter tool with no output schema, it covers prerequisites, enum meaning, side effects, and failure behavior. Gaps: no explanation of projectId and no statement of what a successful confirmation returns or how to correct a wrong preset.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the param burden. It meaningfully interprets a large share of the enum (static, container, and the server presets with HTTP-on-PORT behavior), though the JS presets (nextjs, vite, astro, sveltekit, nuxtjs, react-router, gatsby) and projectId are left unexplained.

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 verb ('Confirm') and resource ('the app type (framework preset) Tofu detected'), plus the scoping moment (before first deploy, before database connection). An agent can tell this is a confirmation/recording step distinct from deploy and database tools.

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

Usage Guidelines4/5

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

Explicit timing guidance: call before the first deploy and before the database is connected, with the reason (browser-facing key names derive from the preset recorded then). It does not name an alternative tool or state what to do if the preset is already confirmed, but the sequencing context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources