GPT-5 MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation3/5
The purposes of consult_gpt5, start_conversation, and continue_conversation overlap somewhat, as all involve interacting with GPT-5. However, get_cost_* and set_cost_* are clearly distinct, and get_conversation_metadata vs summarize_conversation serve different needs.
Naming Consistency4/5
Most tools follow a verb_noun pattern (e.g., start_conversation, get_cost_report, set_cost_limits). The exception is consult_gpt5, which embeds the object directly rather than using a generic noun, but the naming style is otherwise consistent.
Tool Count5/5
With 8 tools, the server is well-scoped for managing GPT-5 conversations and costs. Each tool covers a distinct aspect of the workflow without unnecessary bloat, and the count is appropriate for the domain.
Completeness4/5
The core lifecycle of conversation management and cost control is covered, including starting, continuing, summarizing, and monitoring usage. Minor gaps include the lack of an explicit 'end_conversation' or 'delete_conversation' tool, but agents can likely work around these.
Average 3.1/5 across 8 of 8 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it only mentions planning/coding assistance. It does not disclose potential spending, budget checks, streaming behavior, or cost confirmation implications, despite parameters like task_budget and confirm_spending suggesting these are important.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one concise sentence with no repetition or filler. It is front-loaded and efficient, though slightly terse for the underlying complexity; still, it earns a 4 for its compactness.
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?
Given the complexity of 8 parameters, no annotations, and no output schema, the description is too sparse to provide complete context. It lacks details about spending, streaming, conversation alternatives, and expected return behavior, making it only minimally adequate.
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% since all 8 parameters have descriptions in the schema. The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.
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 uses a specific verb ('Consult') and resource ('GPT-5') with a clear scope ('planning or coding assistance'). However, it does not explicitly distinguish this from sibling tools like start_conversation or continue_conversation, which could also involve consulting GPT-5, so it falls short of 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as start_conversation or continue_conversation. 'Planning or coding assistance' implies a use case, but there are no exclusionary or alternative-recommendation details.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits itself, but it only says 'Return conversation metadata and messages'. It implies a read-only operation but provides no details on response structure, pagination, ordering, or potential side effects. This is minimal disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, short sentence that front-loads the verb and resource. It is appropriately sized for a simple getter tool, with no unnecessary words, though it could include more detail without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity—one parameter, no output schema—the description covers the basic purpose. However, it lacks details on what metadata is returned, message format, or any limitations, leaving some gaps for a complete understanding.
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?
The only parameter, conversation_id, is fully described in the schema as 'Conversation ID', providing 100% schema description coverage. The tool description adds no additional meaning beyond the schema, so the 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 uses a specific verb 'Return' and names the resource 'conversation metadata and messages', which clearly states the tool's purpose. It distinguishes itself from siblings like summarize_conversation or continue_conversation by focusing on metadata and messages, though it does not explicitly name alternatives.
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 is provided on when to use this tool versus alternatives such as get_cost_report or set_conversation_options. The description only states the action, omitting context like prerequisites, use cases, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only says 'Adjust', implying a mutation, but provides no additional behavioral context. It does not disclose whether the adjustment affects ongoing conversations, when changes take effect, whether any special permissions are needed, or what the tool returns. With no annotations to fall back on, the description carries the full burden, and this is insufficient.
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?
The description is a single, compact sentence with no fluff or repetition. It is front-loaded with the verb and the key resource. While it could be more informative, conciseness is about efficiency, and this description achieves that perfectly.
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?
For a mutation tool with no annotations and no output schema, this description is notably incomplete. It does not mention side effects, return values, or how it relates to other conversation-management tools. The agent would need to infer behavior from the schema alone, which is not enough for a tool that modifies state.
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?
The input schema already covers 100% of the parameters, including descriptions for 'budget_limit' (per-conversation budget limit in USD) and 'context_limit' (messages to keep in context window). The description adds a high-level grouping ('budget/context options') but does not provide additional semantics beyond the schema. Thus a baseline score of 3 is appropriate.
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 clearly states the action ('Adjust') and the target ('conversation budget/context options'), which gives a clear sense of the resource. However, it does not explicitly distinguish from the sibling tool 'set_cost_limits', which likely also deals with budget settings. The presence of 'conversation_id' in the schema hints at per-conversation scope, but the description alone does not make that distinction.
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 is provided on when to use this tool versus alternatives. With siblings like 'set_cost_limits' and 'get_conversation_metadata', the agent would benefit from knowing that this tool is for adjusting per-conversation budget/context settings, while 'set_cost_limits' is probably for global cost limits. The description gives no such differentiation or prerequisite information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it offers none. It does not mention spending, side effects, streaming behavior, budget limits, or confirmation requirements, all of which are significant for a tool involving monetary costs and conversation state changes. The description is purely a functional statement with no transparency about how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no wasted words, front-loading the core purpose effectively. However, it is extremely sparse, which slightly undercuts its value as a complete tool description, but for conciseness alone it earns a strong score.
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?
The tool has 6 parameters including financial ones (budget_limit, confirm_spending), a streaming flag, and a token cap, yet the description provides no context about return values, cost implications, required confirmations, or streaming behavior. With no output schema and no annotations, this description is severely incomplete for a tool of this complexity.
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?
The input schema provides 100% coverage of parameter descriptions, so the schema alone adequately documents the parameters. The tool description adds no additional meaning or context beyond the schema, leaving the agent to rely solely on schema descriptions. Per the rubric, baseline 3 is appropriate since schema coverage is high and no extra semantics are provided.
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 'Continue an existing conversation with GPT-5' uses a specific verb (continue) and resource (existing conversation with GPT-5), clearly distinguishing it from sibling tools like start_conversation. It immediately conveys the tool's core action without ambiguity, making it stand out among similar conversational tools.
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?
The description implies usage: use this tool to continue an existing conversation rather than start a new one (contrasting with start_conversation). However, it does not explicitly state when to use this tool over alternatives like consult_gpt5 or summarize_conversation, nor does it mention any exclusions or prerequisites. The context is clear but minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It only states 'Get a report' without detailing return format, how 'current' is interpreted relative to the period parameter, or any other behavioral traits such as read-only nature or potential side effects.
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?
The description is a single concise sentence, front-loaded with the action and resource. Every word earns its place, and there is no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one parameter and no output schema, the description is minimally viable. However, it leaves gaps: it does not explain what 'costs and usage' includes, whether the report is aggregate or detailed, or how the period parameter affects the output. This is adequate but not complete.
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?
The schema has 100% coverage for the single parameter 'period' with a clear description and enum. The tool description itself adds no parameter information, so it meets the baseline of 3 without enhancing semantic understanding.
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 clearly states the tool's function with a specific verb ('Get') and resource ('report of current costs and usage'). It is distinct from sibling tools like set_cost_limits and get_conversation_metadata, though it could more explicitly delineate its scope compared to those.
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 is provided on when to use this tool versus alternatives. Sibling tools exist (e.g., set_cost_limits), but the description does not mention exclusions or direct users to alternative tools for other use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for disclosing behavior. It only says 'Start a new conversation' without mentioning side effects such as creating a new session, potential costs, or what happens to existing conversations. This is a significant transparency gap for a tool that initiates an action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no redundant information. It is efficiently front-loaded and easy to parse, though not as structured as descriptions with multiple sections.
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?
Given the absence of an output schema and annotations, the description should explain what the tool returns (e.g., conversation ID) and provide context about how the parameters interact. It does not, leaving the tool under-specified for agents trying to understand its full effect.
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?
The input schema describes all three parameters (topic, budget_limit, instructions) with 100% coverage. The tool description itself adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.
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 clearly states the action ('Start a new conversation') and the resource ('GPT-5'), making the tool's purpose unmistakable. The word 'new' distinguishes it from the sibling tool 'continue_conversation', though it does not explicitly name alternatives.
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?
The intent is implied: use when you want to begin a fresh conversation. However, there is no explicit guidance about when to choose this over 'continue_conversation' or 'consult_gpt5', nor any mention of prerequisites or exclusion conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It implies mutation via 'Configure' but does not state whether this overwrites existing limits, requires specific permissions, or has any side effects. It also does not describe the response or error behavior.
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?
The description is a single concise sentence that front-loads the action and resource. There is no filler, redundancy, or unnecessary detail. It is appropriately sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with only two optional parameters and no output schema, so the description is close to adequate. However, it lacks usage guidelines and behavioral transparency, making it minimally viable but not fully complete for confident invocation in all scenarios.
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?
The schema already provides 100% coverage with clear descriptions for both parameters (task_limit and daily_limit in USD). The description adds only the context that these are for GPT-5 usage, which is minimal additional meaning beyond the schema.
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 uses a specific verb 'Configure' with resource 'spending limits for GPT-5 usage', clearly distinguishing it from sibling tools like get_cost_report (which reports costs) and set_conversation_options (which sets conversation options). The scope is unambiguous.
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 is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or relationships to siblings like get_cost_report for viewing limits or set_conversation_options for other settings. The usage context is entirely implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It only states that it summarizes to reduce context size but does not disclose whether the conversation is modified, if messages are deleted, whether the operation has side effects, or what happens to the original messages. This is a significant gap for a tool that likely alters conversation state.
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?
The description is a single sentence that efficiently communicates the core function and purpose. It is front-loaded with the action and contains zero filler, making every word earn its place.
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?
The description is insufficient for a tool that likely mutates conversation state, especially with no annotations or output schema. It does not explain what happens to the conversation, what the summary looks like, or how parameters like keep_last_n influence behavior. The complexity and potential side effects demand a more detailed description.
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?
The input schema already describes all three parameters (100% coverage), so the baseline is 3. The description adds no additional parameter semantics—it does not explain how max_tokens or keep_last_n affect the summarization process or how they interact, leaving the schema to carry the full parameter burden.
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 uses the specific verb 'summarize' and resource 'a conversation' with the clear purpose 'to reduce context size'. It distinguishes itself from sibling tools like continue_conversation or start_conversation because none of them mention summarization.
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?
The phrase 'to reduce context size' implies when to use the tool, but it does not explicitly state when not to use it or mention alternatives. No exclusions or comparisons to sibling tools are given, so the guidance remains implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![gpt5_mcp MCP server](https://glama.ai/mcp/servers/andreahaku/gpt5_mcp/badges/card.svg)](https://glama.ai/mcp/servers/andreahaku/gpt5_mcp)

Score Badge

Copy to your README.md:

[![gpt5_mcp MCP server](https://glama.ai/mcp/servers/andreahaku/gpt5_mcp/badges/score.svg)](https://glama.ai/mcp/servers/andreahaku/gpt5_mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andreahaku/gpt5_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server