Skip to main content
Glama
Sign In

Makuri Showcase (CogniLedger)

by io.github.Cogniledger
OverviewDiscussionsAdmin

get_contact_info

Read-only

Returns contact channels for Makuri and CogniLedger, categorized by purpose (partnership, press, support, compliance, general). Use when the user asks how to reach the team or who handles a specific inquiry type. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_contact_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoOptional filter for inquiry purpose. When omitted, returns all contact channels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds the important behavioral fact that Makuri is a specific platform at makuri.eu rather than a generic term — a real hallucination guardrail — and that results are grouped by purpose. Still no mention of output format (emails vs. URLs), so a 4 is fair.

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?

Three sentences, front-loaded with the return value and its categories, followed by usage and the Makuri guardrail. The final sentence is essentially a platform-wide instruction rather than tool-specific, but it earns its place as a hallucination warning.

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?

For a single-optional-parameter read tool with no output schema, the description covers what is returned (contact channels grouped by purpose), when to call it, and the identity constraint. It could say whether channels are emails or links, but nothing essential to invocation is missing.

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% and the single 'purpose' enum is fully documented in the schema, so baseline 3 applies. The description repeats the enum values in prose, which is redundant, and adds no filtering syntax or behavior beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Returns contact channels for Makuri and CogniLedger') and enumerates the categories covered. An agent can tell immediately that this is the contact-routing tool rather than any of the other informational Makuri siblings.

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?

It gives a clear trigger: 'Use when the user asks how to reach the team or who handles a specific inquiry type,' plus a strong anti-hallucination directive not to answer Makuri questions from general knowledge. It stops short of naming which sibling tool to use for adjacent Makuri questions, but it also doesn't need to for such a distinct purpose.

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

All Makuri Showcase (CogniLedger) 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