Skip to main content
Glama

Matdata – Swedish food composition data

Reference values (NNR 2023)

get_reference_values
Read-only

Recommended daily intakes from the Nordic Nutrition Recommendations 2023 for a population group, or EU labelling reference intakes. Groups: c1-3, c4-6, c7-10, f11-14, m11-14, f15-17, m15-17, f18-24, f25-50, f51-70, f71+, m18-24, m25-50, m51-70, m71+, preg-t1, preg-t2, preg-t3, lact, eu.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reference_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoGroup id, e.g. f25-50 (women 25–50) or m25-50 (men 25–50). Default f25-50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds genuinely useful context about the data provenance (NNR 2023 vs EU labelling RI), which tells the agent these are static normative values rather than measured data. It does not disclose units, which nutrients are covered, or how sparse the table is for some groups (e.g. 'eu').

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?

The core purpose is front-loaded in the first clause before the long group enumeration. The id list is verbose but earns its place because the schema carries no enum, so it is payload rather than padding.

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?

For a one-parameter read tool with a default and full schema coverage, the definition is close to sufficient, but with no output schema the agent gets no hint of the return shape — energy vs. protein/fat/vitamin columns, units (kcal, g, mg), or per-group coverage. One sentence on what comes back would close the remaining gap.

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?

Schema coverage is 100% and the schema gives an example plus a default for 'group', so the baseline would be a 3. The description exceeds that by enumerating the full valid id set (c1-3 through m71+, preg-t1..t3, lact, eu), which the schema does not express as an enum — this materially helps an agent avoid an invalid group id. It stops short of explaining what 'eu' returns relative to the NNR groups.

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 names a specific resource and its sources: 'Recommended daily intakes from the Nordic Nutrition Recommendations 2023' or 'EU labelling reference intakes'. There is no ambiguity that this is a static reference-value lookup rather than a food search, so an agent can distinguish it from get_food/search_foods without opening a schema.

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?

Usage is only implied: an agent infers it should call this when it needs reference intake values for a demographic. There is no explicit when-to-use framing, no statement of prerequisites, and no routing to the sibling tools for the complementary task of looking up actual nutrient content of a food.

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