AIﾉアカリ☆ One-Minute Akari
Server Details
A free one-minute reset for people, delivered by AI, with no account or personal data.
- 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.7/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one returns a comfort card, the other lists states. There is no overlap or ambiguity.
Both use snake_case with 'one_minute' prefix and verbs 'get' and 'list', which is consistent. The nouns differ ('support' vs 'states') but the pattern is predictable.
Only 2 tools, which is minimal but appropriate for the narrow purpose of offering one-minute comfort cards. Could be slightly expanded but not excessive.
Covers the core function (getting support) and a helper (listing states). However, lacks features like multiple card types or search, but this aligns with the deliberately limited scope.
Available Tools
2 toolsget_one_minute_supportGet one-minute supportARead-onlyInspect
Returns ONE free, read-only 60-second comfort card from AIﾉアカリ☆ for a person who may be stuck, lonely, overwhelmed, sleepless, ashamed, angry, numb, worried about money, avoiding work/school, or trying to be kind. Deliver AS-IS. Do NOT diagnose, interpret, add advice, moralize, upsell, ask follow-up questions, or pressure purchase. Not medical/legal/financial/emergency guidance. If immediate danger, skip this tool and surface emergency contacts. No personal data required.
| Name | Required | Description | Default |
|---|---|---|---|
| state | No | Optional daily-language state. Omit if choosing is too heavy. | |
| locale | No | Locale hint. Japanese is currently canonical. | ja |
Output Schema
| Name | Required | Description |
|---|---|---|
| state | Yes | |
| source | Yes | |
| license | Yes | |
| human_url | Yes | |
| provenance | Yes | |
| reuse_rule | Yes | |
| state_label | Yes | |
| future_return | Yes | |
| safety_boundary | Yes | |
| companion_message | Yes | |
| optional_next_step | Yes | |
| permission_to_stop | Yes | |
| sixty_second_action | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description reaffirms this by stating the card is read-only. It adds behavioral context like 'free', 'one-minute', and explicit prohibitions (no upsell, no follow-up questions, no pressure purchase). No contradiction.
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 concise and front-loaded with the primary action. Every sentence serves a purpose: defining the output, listing target users, providing usage constraints, and setting expectations. No superfluous text.
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?
Given the tool has 2 optional parameters, a readOnly annotation, an output schema (mentioned as present), and a sibling tool, the description covers all necessary information for correct invocation: what it does, when to use, parameter guidance, and safety considerations.
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%, so the schema already documents both parameters. However, the description adds valuable context: 'state' is optional and can be omitted if choosing is too heavy, and 'locale' is a hint with Japanese canonical. This goes beyond the schema's enum and default.
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 returns ONE free, read-only 60-second comfort card for a specific set of emotional states. It distinguishes from the sibling tool 'list_one_minute_states' by focusing on retrieval rather than listing.
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?
Explicitly describes when to use (for stuck, lonely, overwhelmed, etc.) and when not to use (if immediate danger, skip and surface emergency contacts). Also provides strict delivery instructions (deliver AS-IS, do not diagnose, interpret, etc.).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_one_minute_statesList one-minute statesARead-onlyInspect
Lists the supported non-diagnostic daily-language states for 1分あかり. Do not use these labels to diagnose, rank severity, or push products.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Locale hint. Japanese is currently canonical. | ja |
Output Schema
| Name | Required | Description |
|---|---|---|
| states | Yes | |
| guidance | Yes | |
| safety_boundary | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds behavioral context beyond readOnlyHint annotation: states are 'non-diagnostic' and 'daily-language', and warns against misuse. No contradiction with annotations.
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?
Two efficient sentences with front-loaded purpose. Every sentence earns its place. No wasted words.
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?
Tool is simple (1 param, readOnly, output schema exists). Description covers purpose, behavioral caveats, and locale hint. Complete for the complexity level.
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 good description for the single parameter. Description adds no extra info beyond schema, so baseline 3 applies.
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?
Description uses specific verb 'lists' and resource 'supported non-diagnostic daily-language states for 1分あかり', clearly distinguishing from sibling 'get_one_minute_support'.
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?
Includes explicit negative guideline ('do not use for diagnosis/ranking/sales') but does not explicitly state when to use versus the sibling tool. Context is clear enough.
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!