A
license-
qualityB
maintenanceEnables secure, natural language access to private Cloud SQL PostgreSQL data for catering CRM management, exposing database CRUD operations as MCP tools via Cloud Run.
1
MIT
authenticated-mcp-agent
Server Details
JWT-gated LLM gateway: authenticate (bcrypt/JWT), then run a LangChain-on-Vertex Gemini completion.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mikerawsonnz/gosce-agents
- GitHub Stars
- 1
- Server Listing
- A2A GOSCE Agents
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsA
Average 3.5/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no risk of confusion between different tools. The single tool's purpose is clearly defined.
Naming Consistency5/5
Since there's only one tool, naming consistency is not applicable; it cannot be inconsistent. The name 'invoke' is generic but acceptable.
Tool Count3/5
One tool is borderline for a server that claims to handle both authentication and LLM completion. It may be too few, but it could function as a single endpoint.
Completeness3/5
The tool combines authentication and completion into one action, which may cover the core workflow. However, there are no separate tools for credential management or status checking, leaving potential gaps.
Available Tools
1 toolinvokeAInspect
JWT-gated LLM gateway: authenticate (bcrypt/JWT), then run a LangChain-on-Vertex Gemini completion. Unauthenticated calls are rejected.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON request for this capability (the same body you'd send as an A2A message). |
Tool Definition Quality
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description bears full responsibility. It discloses authentication requirements (JWT, bcrypt) and the underlying model (LangChain-on-Vertex Gemini). It does not detail error responses, return format, or rate limits, but the core behavior is transparent.
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 two sentences with no wasted words. Every sentence provides essential information about auth and functionality.
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 single-parameter tool without output schema, the description covers authentication and model type. It lacks explicit mention of the output format, which would help completeness, but overall it is 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 coverage is 100% with the parameter 'input' described as 'JSON request for this capability...'. The tool description does not add extra parameter context beyond what is already in the schema, so scores at baseline.
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 identifies the tool as a JWT-gated LLM gateway that authenticates and runs a LangChain-on-Vertex Gemini completion. It states a specific verb (run) and resource (completion), but without sibling tools, differentiation is not needed.
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 context by stating it is JWT-gated and that unauthenticated calls are rejected. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceThis is a server that lets your LLMs (like Claude) talk directly to your BigQuery data! Think of it as a friendly translator that sits between your AI assistant and your database, making sure they can chat securely and efficiently.1,618146MIT
- Flicense-qualityDmaintenanceA FastMCP server providing session-based memory and dynamic authentication using LangChain and Google Gemini. It enables persistent conversation history tracking through a session-ID system over HTTP transport.
- Alicense-qualityCmaintenanceA secure tool-execution plane for agentic AI that enforces JWT authentication, rate limiting, prompt-injection inspection, and audit logging, while ingesting downstream OpenAPI endpoints as MCP tools.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.