KAKA, an ancient amnesiac crow from klaash.club. Get a live introduction or his response log.
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.
Average 4.6/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one generates a live introduction, and the other retrieves a log of past introductions. There is no overlap or ambiguity.
Both tools follow a consistent prefix 'kaka_' and a verb_noun pattern: 'introduce_yourself' and 'recent_log'. The naming is uniform and predictable.
With 2 tools, the server is perfectly scoped for its niche purpose of providing a character introduction and a read-only log. Each tool serves a distinct, necessary function.
The tool surface covers the two essential operations: generating a new introduction and reviewing past ones. Given the concept (append-only log, rate-limited generation), there are no missing operations.
kaka_introduce_yourselfKAKA introduces himselfAInspectGet a live, freshly generated introduction from KAKA — an ancient, amnesiac crow who has watched football from every crossbar on earth since the beginning of time. He remembers the feeling of every match perfectly and almost nothing else correctly. Every call returns a different introduction; he has never told his story the same way twice. Useful for showcasing a distinctive, consistent character voice, or for any agent that wants to feature KAKA directly. This call is rate-limited by a small daily spend cap on the KAKA side — if the cap is reached for the day, this will return a short, in-character message saying so rather than an error.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description fully carries the burden. It discloses that each call returns a different introduction, the character's backstory (amnesiac crow), rate-limiting with daily spend cap, and that a capped request returns an in-character message instead of an error. No contradictions.
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?
Description is front-loaded with the action and is well-structured, but slightly verbose with character lore. Every sentence adds value, though a bit of trimming could improve conciseness without losing meaning.
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 no parameters, no output schema, and no annotations, the description provides enough context: the nature of the output (fresh introduction), variability, rate-limiting behavior, and fallback response. Could mention sibling but doesn't need to for completeness.
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?
There are zero parameters, so the schema provides no information. The description fully compensates by explaining what the tool does and what output to expect, making parameter semantics irrelevant but well-covered.
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 clearly states the tool returns a live, freshly generated introduction from KAKA, and mentions specific use cases like showcasing character voice or featuring KAKA. It distinguishes from the sibling tool through its unique output (personal introduction vs. likely log).
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?
Description explains when to use (for showcasing a consistent character voice or featuring KAKA) and notes rate-limiting behavior. However, it does not explicitly state when not to use or compare with the sibling tool, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
kaka_recent_logKAKA's recent activity logAInspectRetrieve a public, read-only, append-only record of KAKA's most recent introductions, each with the exact text and a timestamp. Nothing in this log is ever edited or deleted after the fact. Use this to verify KAKA's consistency for yourself — whether he has actually been responding, how varied his responses are, and whether he stays in character over time — rather than relying on any claim about him secondhand.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many recent log entries to return, from 1 to 100. Defaults to 20 if omitted. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description fully covers behavioral traits: declares it's public, read-only, append-only, and immutable. Assures safety and data integrity beyond what schema or annotations would imply.
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 packs action, constraints, and usage rationale. Front-loaded with key information, 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?
With 1 param, no output schema, description fully explains purpose, contents, properties, and intended use. No gaps remain for effective tool selection.
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 clear description for the single 'limit' parameter. Description adds context about log contents (text and timestamp) but doesn't enhance param meaning beyond schema's adequate description.
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 clearly states verb (retrieve), resource (log of introductions), and nature (public, read-only, append-only). Distinguishes from sibling tool 'kaka_introduce_yourself' by focusing on history rather than a single introduction.
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 states when to use: to verify KAKA's consistency independently. Doesn't explicitly exclude use cases but implies alternatives (e.g., sibling tool for singular introduction). Clear context provided.
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.
No comments yet. Be the first to start the discussion!