auth-token-service
Server Details
Hash passwords with bcrypt and issue/verify JWT session tokens over A2A + MCP.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 3.1/5 across 1 of 1 tools scored.
Only one tool exists, so no inter-tool ambiguity. However, the tool's description bundles multiple distinct operations (hashing, token issue, token verify) into a single entry point, which may confuse an agent about which action to invoke.
The single tool is named 'invoke', which is vague and does not follow a descriptive verb_noun pattern. With only one tool, consistency is not applicable, but the name poorly conveys its purpose.
One tool is insufficient for the described scope of password hashing and JWT management. Typically, separate tools for hashing, token creation, and token verification would be expected, making the count too low.
The single tool attempts to cover multiple operations but likely lacks granularity (e.g., no refresh or revocation). The surface is incomplete for a robust auth service, forcing the agent to rely on a single overloaded tool.
Available Tools
1 toolinvokeBInspect
Hash passwords with bcrypt and issue/verify JWT session tokens.
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON request for this capability (the same body you'd send as an A2A message). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior. It mentions bcrypt and JWT but does not reveal side effects, auth requirements, rate limits, or detailed behavior (e.g., whether it produces output, input format specifics beyond 'JSON'). Minimal transparency.
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?
Single sentence, no fluff, perfectly concise. Every word earns its place.
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?
Despite no output schema, the description lacks details on return values, error handling, or how to specify which operation to perform. Combining two operations without guidance makes it incomplete for an agent to use correctly.
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?
Schema coverage is 100% with a generic description of 'input' as a JSON request. The tool description adds meaning by specifying what the JSON should contain (password hashing or JWT operations), providing critical context beyond the schema's generic phrase.
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 clearly states the tool does password hashing with bcrypt and JWT session token issuance/verification, providing specific verbs and resources. However, it lumps two distinct operations together without differentiation, which slightly reduces clarity. No siblings exist, so no need for distinction.
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?
No guidance on when to use this tool versus alternatives (none provided). There is no explanation of when to hash vs verify, nor any prerequisites or context for use. The description simply states what it does, not when to use it.
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!