Skip to main content
Glama
Sign In

PromptGPT

by io.promptgpt
OverviewDiscussionsAdmin

Sync PromptGPT Account

syncAccount

Links and synchronizes the user's PromptGPT account with ChatGPT using their Sync Key (e.g. PG-XXXXX). Call this whenever the user provides a sync key (starting with PG-), token, or asks to link/connect their PromptGPT account.

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": {
      "key": "<key>"
    },
    "name": "syncAccount"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe PromptGPT sync key, starting with PG- (e.g. PG-3BC2A).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

The only annotation is a title, so the description carries the full burden. It discloses that this is an account-pairing operation requiring a Sync Key, but says nothing about whether syncing is idempotent, what permissions or existing ChatGPT session it needs, whether it can be undone/revoked, or what happens if the key is invalid or expired.

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?

Two sentences, zero waste: what the tool does first, then the trigger condition. Front-loaded and easy to scan.

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 one-parameter tool with no output schema, the description covers purpose, trigger, and credential format adequately. It leaves the agent guessing about the post-sync state and error cases, but nothing essential for making the call correctly is missing.

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% and the schema already documents the `key` parameter with the PG- prefix and an example. The description restates the same example and broadens the trigger to 'token', adding only marginal semantics beyond the schema. Baseline 3 is appropriate.

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 pair (links and synchronizes) plus the exact resource (PromptGPT account to ChatGPT) and the credential used (Sync Key). An agent can distinguish this from generatePrompt/optimizePrompt, which are prompt-manipulation tools with no account-linking role.

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?

Gives an explicit firing condition: call whenever the user supplies a PG- key, a token, or asks to link/connect their account. It stops short of naming when NOT to call or what to do if the key is malformed or already linked, so it is clear context without exclusions.

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

All PromptGPT toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources