Skip to main content
Glama

joiva_search_foods

Read-onlyIdempotent

Search the signed-in user's own and the shared Joiva food catalog by name. Hits carry per-100g nutrients, per-nutrient provenance (microsOrigin) and product traits (garung/behandlung as bought, sorte, herkunft, weidehaltung). Every food carries brand and certifications (bio, demeter, bioland, naturland, fairtrade; null = none known), which tell products of different makers apart.

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": {
      "query": "<query>"
    },
    "name": "joiva_search_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in disclosing what hits contain: per-100g nutrients, provenance, and traits. It also clarifies null certification semantics, which is genuinely beyond the annotations.

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?

Purpose is front-loaded in the first clause and the total length is short. The middle sentence is dense with unexplained German field names (garung, behandlung, sorte, herkunft, weidehaltung), which adds some noise without defining terms.

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?

There is no output schema, so the description correctly spends its words on return content (nutrients, provenance, brand, certifications), which covers the main gap. However, result ordering/ranking, case sensitivity, and behavior when nothing matches are left entirely unstated for a search tool.

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 0%, so the description must carry parameter meaning; it explains that the query matches food names, but the limit parameter (1-50) is never mentioned. For two simple, largely self-evident parameters this is adequate but not complete.

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

Purpose4/5

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

States a specific verb and resource ("Search ... food catalog by name") plus scope (signed-in user's own and shared catalog). It does not explicitly differentiate itself from lookalike siblings such as joiva_list_frequent_foods or joiva_log_food, which would have earned a 5.

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?

"Search ... by name" implies the lookup use case, but there is no statement of when to prefer this over list_frequent_foods, or what to do when search yields nothing (e.g. joiva_report_food to add a missing product). Usage is implied rather than guided.

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.

Resources