Skip to main content
Glama
Sign In

AfriResolve

by io.github.AFRIRESOLVE
OverviewDiscussionsAdmin

find_foods_by_category

Find African foods by category such as grain, root, fruit, legume, seed, tuber, vegetable, or leafy_vegetable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "find_foods_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesFood category to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

There are no annotations to offload behavioral disclosure, so the description must carry the full burden. It does not mention side effects, whether the operation is read-only, or what the return format is. While 'find' implies a read operation, this is not explicitly stated, and the output shape is left undefined.

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, concise sentence that directly states the purpose and gives examples. No redundant information or fluff; it is well-structured and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (single parameter, no output schema), the description is adequate for basic intent, but it lacks details about the result format (e.g., list vs. single item, ordering, pagination). Since there is no output schema to fill this gap, the description could be more complete by mentioning what the output looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter 'category' has a basic schema description ('Food category to search for'), but the tool description adds valuable context by listing example categories (grain, root, fruit, legume, etc.). This effectively defines the expected input domain beyond the bare schema, though it does not provide an exhaustive list or constraints.

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 tool's purpose: finding African foods by category. It names the resource (African foods), the action (find), and provides concrete examples of accepted categories (grain, root, fruit, etc.), leaving no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives (e.g., find_foods_by_country). While the category-based scope is implicit, no direct guidance or comparison to sibling tools is provided, leaving the selection criteria unstated.

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

All AfriResolve 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