Skip to main content
Glama

Refresh Access Token

neuron_refresh_token
Idempotent

Refresh the access token. Uses the refresh token kept from the last login or org switch in this session; tokens are never shown. Sets the new access token for subsequent API calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "neuron_refresh_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshTokenNoOnly if this session has none kept (e.g. after a restart)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / refreshToken / description
      Previous value: -"Refresh token obtained from the initial login response"New value: +"Only if this session has none kept (e.g. after a restart)"
    • removedInput schema / required
      Removed value: -[
      -  "refreshToken"
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but idempotent, non-destructive, closed-world operation. The description adds genuine context beyond that: the token is drawn from session state, credentials are never returned ('tokens are never shown'), and the call mutates session state so subsequent API calls use the new token. That last point is exactly the side-effect an agent needs to understand.

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, front-loaded with the action, then the token source, then the effect. No filler and nothing buried.

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 parameterless-by-default auth tool with no output schema, the definition covers the important ground: token source, no credential exposure, and session-mutating effect. It leaves out failure behavior (e.g. what happens if no refresh token is available and none is supplied), but nothing an agent needs to invoke it correctly.

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 coverage is 100%, so the single optional refreshToken parameter is already fully documented, including its 'only if this session has none kept' note. The description's statement that the token comes from the session reinforces the optionality but does not add new syntax or format detail, so baseline 3 applies.

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 states a specific verb and resource ('Refresh the access token') and immediately clarifies the source of the refresh token, so an agent knows exactly what operation this performs. It does not explicitly distinguish itself from the auth-adjacent siblings neuron_login/neuron_logout, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of 'the last login or org switch in this session' hints this is the mid-session token-renewal path rather than neuron_login, but there is no explicit when-to-call trigger (e.g. expired token / 401) and no when-not-to-use guidance. An agent can infer the role, but must do the inferring.

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