GPT-5: GPT‑5 is OpenAI’s most advanced and unified AI model, combining fast, real-time.
Creates a model response for the given chat conversation Billing per call: Credits: metered (~0 avg).
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON request body. Example: {"model":"GPT-5","stream":false,"messages":[{"role":"user","content":"There are ten birds in a tree. A hunter shoots one. How many are left in the tree?"}]} |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full behavioral disclosure burden. It does disclose billing/cost behavior and that the tool generates a model response, but it does not mention side effects, auth requirements, response format, streaming, or rate limits. Some transparency is present, but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the core action. The billing note is useful but awkwardly appended without a period, slightly reducing readability. No words are wasted, though formatting could be improved.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a single flexible body parameter and a helpful example, but there is no output schema and the description does not explain return values, error behavior, or usage constraints. Billing is covered, but broader operational context is thin.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is only one parameter, 'body', and the schema provides a description plus a concrete example, giving 100% schema_description_coverage. The description text adds no extra parameter-level detail beyond billing, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Creates a model response for the given chat conversation.' This clearly identifies the tool's purpose and is not a tautology. Even without sibling tools to differentiate from, the action and target are unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is implied: this tool is for generating chat completion responses. However, there is no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. With no sibling tools listed, this is acceptable but leaves usage boundaries unstated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
post_chat_completionsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
GPT-4o: GPT-4o (“o” for “omni”) is our versatile, high-intelligence flagship model. It accepts both.
Swift AI: Access a wide range of AI models⚡, including OpenAI 🤖,DeepSeek 🔍, Claude 🧠, Gemini 🌟, and.
Image, video, music and text generation across 100+ models through one endpoint.
Image, video, audio, face-swap, talking avatars and chat across 300+ AI models, one balance.
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusion or overlap. The single tool clearly covers its intended purpose without competing alternatives.
The tool name 'post_chat_completions' follows a clean verb_noun snake_case convention, matching the style expected for HTTP method and resource. Even in isolation, it is predictable and self-descriptive.
A single tool is on the low end of the spectrum, making the server feel minimal but not unreasonable for a narrowly scoped chat completion endpoint. It could benefit from a couple of supporting tools (e.g., model listing or health check) to feel fully featured.
The server exposes only one operation with no ability to list models, retrieve request logs, or check service status. While the core generation is present, the absence of any auxiliary endpoints leaves notable gaps for real-world usage.
