find_groceries
Search fresh groceries available for delivery in Kenya (Dishi Fiti, food as medicine).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | optional item name, e.g. milk |
mkliniki
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states a search operation but does not disclose if it is read-only, any authentication needs, rate limits, or side effects. The lack of behavioral detail is a gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single 12-word sentence that is front-loaded with verb and resource. Every word is necessary; no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is too brief. It lacks details on return format, how to use the optional query, or any constraints. A simple search tool may suffice, but more context would help.
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 covers 100% of the single parameter with a description ('optional item name, e.g. milk'). The tool description adds context about fresh groceries in Kenya but does not enhance parameter meaning beyond the schema. Baseline 3 is appropriate.
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 clearly states the verb 'Search', the resource 'fresh groceries', and the context 'available for delivery in Kenya (Dishi Fiti, food as medicine)'. This distinguishes it from sibling tools like find_doctor and find_medicine, which focus on medical services.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for searching groceries within a specific program but does not explicitly state when to use this tool over alternatives like find_medicine. No when-not or exclusion criteria are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool targets a distinct aspect: general info, doctor search, grocery search, medicine search, and onboarding. Their descriptions clearly differentiate them, leaving no ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (about_mkliniki, find_doctor, find_groceries, find_medicine, join_mkliniki). No deviations.
Tool Count5/5
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.
Completeness4/5
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.