Skip to main content
Glama
Sign In
Scalekit MCP Server

Scalekit MCP Server

Official
by scalekit-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_mcp_server

Idempotent

Update a registered MCP server name, URL, description, or token lifetime by id. Clear an external provider by switching to Scalekit authentication.

Instructions

Update fields on one registered MCP server, such as its name or URL. Use switch_mcp_auth_to_scalekit when the only change is to clear an external provider and use Scalekit authentication. Use list_mcp_servers to find the id. Requires the caller OAuth token.

Input Schema

NameRequiredDescriptionDefault
idYesRegistered MCP server id. Format: app_<id>.
nameNoNew display name. Omit it to leave the name unchanged.
providerNoConnection key id, in capital letters, when not using Scalekit authentication. Leave empty when useScalekitAuthentication is true.
descriptionNoNew explanation of the server. Omit it to leave the description unchanged.
mcpServerUrlNoNew public URL. This URL becomes the token audience. Omit it to leave the URL unchanged.
environmentIdYesScalekit environment id. Format: env_<id>.
accessTokenExpiryNoNew access token lifetime in seconds. Omit it to leave the lifetime unchanged.
useScalekitAuthenticationYesTrue moves the server onto Scalekit authentication and clears the provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.1
    • addedInput schema / properties / accessTokenExpiry / description
      Added value: +"New access token lifetime in seconds. Omit it to leave the lifetime unchanged."
    • addedInput schema / properties / description / description
      Added value: +"New explanation of the server. Omit it to leave the description unchanged."
    • addedInput schema / properties / environmentId / description
      Added value: +"Scalekit environment id. Format: env_<id>."
    • addedInput schema / properties / id / description
      Added value: +"Registered MCP server id. Format: app_<id>."
    • addedInput schema / properties / mcpServerUrl / description
      Added value: +"New public URL. This URL becomes the token audience. Omit it to leave the URL unchanged."
    • addedInput schema / properties / name / description
      Added value: +"New display name. Omit it to leave the name unchanged."
    • addedInput schema / properties / provider / description
      Added value: +"Connection key id, in capital letters, when not using Scalekit authentication. Leave empty when useScalekitAuthentication is true."
    • addedInput schema / properties / useScalekitAuthentication / description
      Added value: +"True moves the server onto Scalekit authentication and clears the provider."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, non-open-world mutation, so the safety profile is covered. The description adds the caller OAuth token requirement, which is useful context, but says nothing about partial-update semantics or what happens to the provider on the Scalekit path beyond what the schema states.

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?

Three short sentences, each doing distinct work: what it does, the sibling it is not, and how to get the id. Front-loaded with the core action and zero filler.

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 an 8-parameter mutation tool with no output schema, the description covers purpose, sibling routing, id lookup, and the auth prerequisite, leaving only edge cases like provider-clearing behavior on partial updates unaddressed. Annotations and the fully documented schema carry the remaining burden.

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 every parameter including the 'omit to leave unchanged' semantics is already documented in the schema. The description adds no parameter-level syntax or constraint beyond that baseline.

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 (update) and resource (one registered MCP server) and names concrete examples of updatable fields (name, URL). It is clearly distinguishable from siblings register_mcp_server and switch_mcp_auth_to_scalekit, which it explicitly references.

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?

Names the alternative tool switch_mcp_auth_to_scalekit and the exact condition that selects it ('when the only change is to clear an external provider'), and points to list_mcp_servers to obtain the id. Routing guidance is explicit rather than implied.

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