Skip to main content
Glama

AIﾉアカリ☆ One-Minute Akari

by ai.ai-akari
OverviewDiscussionsAdmin

Get one minute of Akari support with an optional state

get_one_minute_support

Use this when a person needs a free 60-second support response and a state hint is already available. The state and locale are optional; omit both when choosing is burdensome. Japanese: 状態が分かる場合だけ補助指定できる互換ツールです。選択が重い時は引数を省略してください。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoOptional state ID. Omit when choosing is burdensome.
localeNoOptional locale hint.ja

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes
sourceYes
licenseYes
embed_urlYes
human_urlYes
provenanceYes
reuse_ruleYes
state_labelYes
future_returnYes
safety_boundaryYes
companion_messageYes
optional_next_stepYes
permission_to_stopYes
sixty_second_actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Locale hint. Japanese is currently canonical."New value: +"Optional locale hint."
    • changedInput schema / properties / state / description
      Previous value: -"Optional daily-language state. Omit if choosing is too heavy."New value: +"Optional state ID. Omit when choosing is burdensome."
    • addedOutput schema / properties / embed_url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "state",
-  "state_label",
-  "sixty_second_action",
-  "permission_to_stop",
-  "companion_message",
-  "future_return",
-  "optional_next_step",
-  "human_url",
-  "safety_boundary",
-  "source",
-  "provenance",
-  "license",
-  "reuse_rule"
-]New value: +[
+  "state",
+  "state_label",
+  "sixty_second_action",
+  "permission_to_stop",
+  "companion_message",
+  "future_return",
+  "optional_next_step",
+  "human_url",
+  "embed_url",
+  "safety_boundary",
+  "source",
+  "provenance",
+  "license",
+  "reuse_rule"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / human_url
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "state",
-  "state_label",
-  "sixty_second_action",
-  "permission_to_stop",
-  "companion_message",
-  "future_return",
-  "optional_next_step",
-  "safety_boundary",
-  "source",
-  "provenance",
-  "license",
-  "reuse_rule"
-]New value: +[
+  "state",
+  "state_label",
+  "sixty_second_action",
+  "permission_to_stop",
+  "companion_message",
+  "future_return",
+  "optional_next_step",
+  "human_url",
+  "safety_boundary",
+  "source",
+  "provenance",
+  "license",
+  "reuse_rule"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations provide no useful positive behavioral hints (all false), and the description does not disclose any behavioral traits beyond the core function. It does not mention side effects, permissions, rate limits, or any effects on state. There is no contradiction, but the description fails to expand on behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English description is concise (two sentences) and front-loaded with the purpose. However, the Japanese sentence repeats the same information in English, adding unnecessary length for an English-speaking agent. Still, it's compact overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (two optional parameters) and presence of an output schema, the description sufficiently covers usage and parameter decisions. It doesn't describe return values, but the output schema covers that. The description could mention prerequisites, but none are apparent.

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%, so the schema fully documents both parameters. The description adds a minor nuance: both parameters can be omitted when choosing is burdensome, extending the schema's note for state to locale. This is a slight improvement but not substantial, keeping the score at baseline 3.

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 states the tool's purpose: retrieve a free 60-second support response, optionally using a state hint. This is specific and matches the title, but it does not explicitly differentiate from sibling tools like one_minute_akari or list_one_minute_states.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: use when a state hint is already available, and omit parameters when choosing is burdensome. It does not explicitly mention when not to use it or alternatives, but the condition 'state hint is already available' implies a scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIﾉアカリ☆ One-Minute Akari toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources