kaka-mcp-server
Server Details
KAKA, an ancient amnesiac crow from klaash.club. Get a live introduction or his response log.
- 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.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.
Available Tools
2 toolskaka_introduce_yourselfKAKA introduces himselfAInspect
Get 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 | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description fully covers behavioral traits: every call returns a different introduction (non-idempotent), rate-limited with a daily spend cap, and a graceful fallback message when the cap is reached.
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 informative and front-loaded with the purpose, but it is somewhat lengthy with creative flavor. Every sentence adds value, though a touch more conciseness would improve it.
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 zero parameters, no output schema, and a single sibling tool, the description covers purpose, usage, behavioral transparency, and error handling completely. No gaps remain.
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 no parameters, so the baseline is 4. The description does not add parameter-specific information, but none is needed.
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 action: 'Get a live, freshly generated introduction from KAKA — an ancient, amnesiac crow.' It distinguishes from the sibling tool 'kaka_recent_log' by focusing on the character introduction rather than logs.
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?
The description explicitly notes use cases: 'useful for showcasing a distinctive, consistent character voice, or for any agent that wants to feature KAKA directly.' It also mentions rate-limiting behavior but does not explicitly state when not to use it.
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 logAInspect
Retrieve 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. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description declares the tool is read-only and append-only, noting that entries are never edited or deleted. With no annotations provided, this fully discloses behavioral traits like idempotency and safety.
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 three sentences with no filler. First sentence states core function, second explains immutability, third provides context for use. Every sentence 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?
Given the simple tool with one well-documented parameter and no output schema, the description fully explains what it does, what it returns, and why it matters. No gaps remain.
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?
The input schema has full coverage (100%) with a description for the 'limit' parameter. The tool description does not add additional meaning beyond the schema, so baseline 3 is appropriate.
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 it retrieves a public, read-only, append-only record of recent introductions with exact text and timestamps. It distinguishes itself from the sibling tool kaka_introduce_yourself by focusing on past records rather than generating new introductions.
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?
The description explicitly says to use this for verifying consistency and character over time, as opposed to relying on secondhand claims. While it doesn't explicitly mention when not to use it, it provides a clear use case.
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!