Skip to main content
Glama

Matdata – Swedish food composition data

Search foods

search_foods
Read-only

Search the Swedish Food Agency food composition database (2,600 foods) by name in Swedish or English. Returns id, name, energy (kcal per 100 g) and URL. Use the id with get_food.

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": "search_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of names in the result (default: sv)
limitNoMax results (default 10)
queryYesFood name, e.g. 'havregryn' or 'rolled oats'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 safety is covered; the description adds real context beyond that by disclosing the return fields (id, name, energy kcal/100 g, URL) and the bilingual name matching. It does not mention whether an empty result is possible or how matching is performed (prefix vs substring), which keeps it from a 5.

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?

Three short sentences, zero filler: dataset scope, return shape, and next step in that order. The most decision-relevant information (what it searches and what comes back) is front-loaded.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the return fields, and the small 3-parameter surface is fully covered by the schema. An agent has everything needed to call it and to act on the result.

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%, so query, lang, and limit are already documented with examples and defaults. The description only adds the note that names can be Swedish or English, which marginally clarifies query semantics but does not extend the schema's meaning; baseline 3 applies.

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?

Names a specific verb and resource plus the exact dataset (Swedish Food Agency food composition database), its size (2,600 foods), and the accepted name languages. An agent can distinguish it from get_food, compare_foods, and top_foods purely from this sentence.

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?

Explicitly routes the agent forward: 'Use the id with get_food' tells the agent this is a lookup/discovery step feeding a detail call. No when-not-to-use or exclusion against top_foods/compare_foods is stated, so it stops short of a 5.

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