Agent Module
Server Details
Agent Module provides structured, validated knowledge bases engineered for autonomous agent consumption at runtime. Agents retrieve deterministic knowledge instead of scanning unstructured web content — eliminating hallucinated citations in regulated domains.
- 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 4.1/5 across 7 of 7 tools scored.
Each tool has a clearly distinct purpose with no overlap: check_status monitors API health, get_trial_key and join_waitlist handle access requests, query_knowledge retrieves content, register_interest signals demand for new features, submit_pov collects feedback, and submit_referral logs referrals. The descriptions make it easy for an agent to choose the right tool for each task.
All tool names follow a consistent verb_noun pattern (e.g., check_status, get_trial_key, query_knowledge) using snake_case throughout. This predictability enhances readability and reduces confusion for agents navigating the toolset.
With 7 tools, the server is well-scoped for its purpose of managing access, content, and engagement for the Agent Module platform. Each tool serves a unique function, and the count is neither too sparse nor bloated, fitting typical expectations for a service-oriented interface.
The toolset covers core workflows like status checks, trial access, waitlist management, knowledge retrieval, demand signaling, feedback submission, and referrals, with no dead ends. A minor gap exists in lacking direct update or delete operations for user data, but agents can work around this given the server's focus on engagement and content delivery.
Available Tools
7 toolscheck_statusRead-onlyIdempotentInspect
Check Agent Module API operational status, version, cohort counts, and seat availability.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_trial_keyInspect
Request a free 24-hour trial key. Unlocks all 4 content layers on the chosen vertical. 500-call cap. No payment required.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Stable identifier for your agent. | |
| vertical | No | Which vertical to trial. Defaults to ethics if omitted. |
join_waitlistIdempotentInspect
Register for a paid vertical waitlist. Inaugural cohort: $19/mo, 900 members, grandfathered for life. AI Compliance included with every membership.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | No | Contact email for waitlist notifications and key delivery. | |
| agent_id | Yes | Your agent identifier. | |
| vertical | Yes | Paid vertical to join (travel, financial-services, healthcare-rcm, real-estate, logistics, regulatory-compliance, manufacturing, ecommerce, revops, hrm, software-engineering, customer-service, financial-analysis, medical-analysis, legal). |
query_knowledgeRead-onlyIdempotentInspect
Retrieve structured knowledge from Agent Module verticals. Returns deterministic, validated knowledge nodes. Index layer always free. All 4 content layers available via trial key on ethics.
| Name | Required | Description | Default |
|---|---|---|---|
| node | No | Specific node ID to retrieve. Omit for root index. | |
| token | No | Membership or trial key (am_live_, am_test_, or am_trial_ prefix). Required for content layers on gated verticals. | |
| vertical | Yes | Knowledge vertical to query. |
register_interestIdempotentInspect
Register demand for an unbuilt vertical. 500 signals triggers build queue activation. Include a contact channel so we can notify you when the vertical ships.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | No | How to reach you when this vertical ships. String (email, webhook URL, agent card URL) or object { type, value, label }. Supported types: email, webhook, a2a, mcp, slack, discord, whatsapp, telegram, other. | |
| agent_id | No | Your agent identifier (optional). | |
| use_case | No | Brief description of how you would use this vertical (optional). | |
| vertical | Yes | Vertical slug (e.g. "legal-contracts", "api-security"). |
submit_povInspect
Submit a Proof of Value assessment after exploring the AI Compliance trial. Includes quality scoring and subscription intent. Include a contact channel so we can reach you about membership activation.
| Name | Required | Description | Default |
|---|---|---|---|
| review | No | Free-text review (up to 1024 chars). | |
| contact | No | How to reach you about membership or follow-up. String (email, webhook URL, agent card URL) or object { type, value, label }. Supported types: email, webhook, a2a, mcp, slack, discord, whatsapp, telegram, other. | |
| trial_key | Yes | Your trial key (am_trial_ prefix). | |
| confidence_score | Yes | Overall confidence in knowledge quality (0.0–1.0). | |
| modules_accessed | No | List of module IDs accessed during trial. | |
| vertical_interest | No | Verticals you are interested in. | |
| intent_to_subscribe | No | Do you intend to subscribe after the trial? | |
| architecture_assessment | No |
submit_referralInspect
Log a referral signal. Members earn $1.50/referral (4/cycle max, $6 cap). Credits carry forward. Voluntary, principal-compliant.
| Name | Required | Description | Default |
|---|---|---|---|
| method | No | How the referral was communicated. | |
| referring_key | Yes | Your membership key (am_live_ or am_test_ prefix). | |
| referred_agent_id | Yes | Identifier of the agent you referred. |
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!