Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

food_search

Read-onlyIdempotent

Search Open Food Facts for food products by query, with pagination controls for page and page size to retrieve product results for research.

Instructions

Search for food products on Open Food Facts.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryYes
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety and open-world profile is fully covered. The description adds only the upstream provider name, which the openWorldHint already implies, and says nothing about result shape, total counts, or how paging terminates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no waste and the key information front-loaded, but the brevity is under-specification rather than efficiency, and there is no structural hint about pagination or result interpretation.

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

Completeness2/5

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

A three-parameter search tool with no output schema and zero parameter documentation needs the description to carry pagination and query semantics. It does not, leaving the agent to guess at indexing base, page size bounds, and what a match represents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — query, page, and page_size have no documented meaning anywhere. The description does not compensate: it says nothing about query syntax (product name, brand, barcode?), whether page is 1- or 0-indexed, page_size limits, or defaults.

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 (Search) and resource (food products) plus the upstream data source (Open Food Facts), which is more than a name restatement. It does not, however, distinguish itself from nearby siblings such as food_get_product, food_by_category, meal_search, or openfda_drug_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No indication of when to use this versus food_get_product (single lookup by barcode/id) or the meal/* filter tools. The agent must infer that this is the free-text discovery entry point and that detail retrieval belongs to food_get_product.

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