Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-refreshToken

Idempotent

Refreshes an application's token using its application ID, restoring authenticated access when the existing token needs renewal.

Instructions

POST /application.refreshToken

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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-refreshToken"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

The annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows it touches external state and can be retried safely. The description adds nothing beyond the route: it does not say whether the previous token is revoked, how long the new token lives, what permissions are required, or what the response contains. For a credential-minting operation this silence is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is brief, but this is under-specification rather than conciseness: a single route string earns nothing for the reader. There is no front-loaded statement of effect, so brevity is not a virtue here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A one-parameter mutation tool with no output schema, 0% parameter documentation, and only two hints in annotations requires the description to explain the operation and its consequences. The description supplies none of that, so an agent cannot call it correctly on the basis of this definition alone.

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% for the single required parameter, applicationId, so the description must carry the meaning and does not. It never says whether applicationId is the application whose token is being rotated or what form the identifier takes, leaving the schema's bare string type as the only information.

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

Purpose2/5

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

The description restates the tool name as an HTTP route ("POST /application.refreshToken") without saying what refreshing a token accomplishes, whether it mints a new token, invalidates the old one, or what is returned. It conveys only a verb-ish hint (POST) and the resource, and offers no differentiation from siblings such as compose-refreshToken, user-generateToken, or scim-generateToken.

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?

There is no when-to-use guidance, no prerequisites, and no stated alternative. With several token-related siblings present, an agent has no basis in the description for choosing this tool over compose-refreshToken or user-generateToken.

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