How to JOIN M-Kliniki. Use this when the user is a LICENSED PROVIDER (doctor, pharmacy, laboratory), a grocer or shop, a delivery rider, an ambulance, or a partner or investor wanting to reach more customers in Kenya and get paid automatically, or a patient or buyer who wants to start. Returns the right onboarding path.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | one of: doctor, pharmacy, laboratory, grocer, rider, ambulance, patient, partner, investor |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. It states the tool returns the right onboarding path, but lacks details on side effects, authentication, or what 'onboarding path' entails. Adequate but not comprehensive.
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 sentences, 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?
Given low complexity (one parameter, no output schema), description adequately covers when to use and general behavior. Could specify return type more precisely, but acceptable.
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 description adds minimal value beyond listing roles already in schema. Helpful enumeration, but not essential.
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's purpose: joining M-Kliniki for specific roles. It distinguishes from siblings like about_mkliniki and find_* tools by focusing on onboarding.
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 lists when to use: for licensed providers, grocers, riders, patients, etc. Implicitly excludes use for information or search queries, which are covered by sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect: general info, doctor search, grocery search, medicine search, and onboarding. Their descriptions clearly differentiate them, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (about_mkliniki, find_doctor, find_groceries, find_medicine, join_mkliniki). No deviations.
With 5 tools, the server is well-scoped for its purpose of providing health and grocery services in Kenya. Each tool serves a clear function without unnecessary redundancy.
The toolset covers core functionalities: information, finding doctors, groceries, OTC medicine, and onboarding. Minor gaps like missing appointment booking or account management exist but are reasonable given the focused scope.