Skip to main content
Glama

get_custom_foods

Read-only

Search and list your custom foods to find existing entries by name, avoid duplicates, and retrieve food and serving IDs for logging.

Instructions

Search or list user's custom foods

    Returns custom foods the user has created. Use the search parameter
    to find existing foods by name before creating duplicates — the
    response includes foodId and servingId needed for log_custom_food.

    For branded catalog foods (FatSecret), use search_foods instead.

    Args:
        search: Search term to filter foods by name (default: list all)
        start: Starting index for pagination (default 0)
        limit: Maximum number of results (default 20)
    

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_custom_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's job is to add workflow context — which it does by disclosing that the response carries foodId and servingId needed for log_custom_food, plus pagination defaults. It does not mention whether a total count is returned or any rate/limit behavior, leaving a small gap.

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?

Front-loaded with purpose and the dedupe/search-before-create guidance, then the sibling exclusion, then parameters. The docstring-style Args block repeats defaults already present in the schema, which is mild waste but keeps the definition scannable.

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

Completeness4/5

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

No output schema exists, and the description compensates by naming the key return fields (foodId, servingId) and their downstream use. Pagination is described only as start/limit with no mention of total counts or how to know when results end, which is the main remaining gap for a paged list tool.

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 description coverage is 0%, so the description must carry all parameter meaning, and it does: search filters by name with list-all as the fallback, start is a pagination offset, limit caps results. The defaults it restates duplicate the schema, which slightly dilutes the added value but the semantic explanation is genuinely new.

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?

States a specific verb and resource ('Search or list user's custom foods') and immediately scopes it against the closest sibling by excluding branded catalog foods. An agent can tell this apart from search_foods and get_custom_food_serving_units 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 Guidelines5/5

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

Gives an explicit pre-workflow instruction ('use the search parameter to find existing foods before creating duplicates') and an explicit alternative for the out-of-scope case ('For branded catalog foods (FatSecret), use search_foods instead'). Both when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools