Skip to main content
Glama
Sign In
Git MCP Server

Git MCP Server

by yumeminami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

refresh_platform_username

Refresh the username for a configured platform by retrieving the new username from the authentication token.

Instructions

Refresh username for a configured platform by fetching from token

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": {
      "platform": "<platform>"
    },
    "name": "refresh_platform_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It says 'fetching from token' but does not clarify if this is a read-only refresh or if it modifies stored data. It lacks details on authorization requirements, side effects, or reversibility.

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?

A single sentence conveys the essential action and mechanism. No redundant words, front-loaded with the verb 'Refresh'.

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

Completeness2/5

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

Despite having an output schema, the description does not mention what is returned. For a simple tool, it still lacks completeness regarding prerequisites, use cases, and behavioral implications.

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?

The only parameter 'platform' has no description in the schema (0% coverage). The description adds only the phrase 'for a configured platform', which provides minimal context. No constraints, examples, or enumeration are given.

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?

The description clearly states the action (refresh), the object (username), and the mechanism (fetching from token). It distinguishes itself from siblings like list_platforms and test_platform_connection by focusing on a specific update operation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Does not mention prerequisites such as the platform being configured or having a valid token, nor when a refresh is necessary.

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