Skip to main content
Glama
Sign In

CoKarTa

by com.cokarta.app
OverviewDiscussionsAdmin

List foods

list_foods
Read-onlyIdempotent

Lists the person's food catalog and favourite dishes, optionally filtered by name, with the energy and macros each food holds.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional name filter: one term, or several separated by commas.
detailNoAsk for the whole label instead of the four-value summary: all eight values on both bases, plus brand, description and what the food is measured in. Use it when the question is about a value the summary does not print — saturates, sugars, fibre or salt — or about how a food is recorded. It prints the same block a write returns, so one call answers for every food it lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered without the description. The description adds that results carry per-food energy and macro values, but says nothing about ordering, completeness, or what the default (summary) payload contains beyond those figures.

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?

A single front-loaded sentence with no filler: verb, resource, optional filter, and returned fields in order of importance. Nothing could be removed without losing information.

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?

For a simple, non-destructive list tool with full schema coverage, no output schema, and annotations covering safety, this is close to complete. The only gap is that return-cardinality and ordering behavior are not described, which matters little for a catalog listing.

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 description coverage is 100%, so both the query filter and the detail flag are fully documented in structured fields; the baseline of 3 applies. The description's only added meaning is 'optionally filtered by name,' which the schema already states more precisely as a comma-separated term list.

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?

The description opens with a specific verb and resource: 'Lists the person's food catalog and favourite dishes,' and adds what data comes back (energy and macros). It is clearly a read of stored foods, distinguishable from write siblings like save_food and save_dish, though it never names an alternative read tool.

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: 'optionally filtered by name' tells the agent the filter is optional but gives no explicit when-to-use or when-not-to-use guidance versus siblings such as read_diary. The richer conditional guidance for the detail flag lives in the schema, not in the description.

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

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