Skip to main content
Glama
Sign In
FatSecret MCP Server

FatSecret MCP Server

by fliptheweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

autocomplete_foods

Read-onlyIdempotent

Get autocomplete suggestions for a partial food search expression to quickly find matching foods as you type.

Instructions

Get autocomplete suggestions for a partial food search expression. Premier exclusive.

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": {
      "expression": "<expression>"
    },
    "name": "autocomplete_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
languageNo
expressionYesPartial search expression
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.9

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds the 'Premier exclusive' constraint, which is valuable behavioral context beyond annotations. No contradictions found.

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?

The description is very concise with two short sentences. It is front-loaded with purpose. However, it is under-specified given the tool has four parameters and no output schema, sacrificing completeness for brevity.

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

Completeness1/5

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

The description is highly incomplete. It does not explain the return format (autocomplete suggestions), the effect of optional parameters, or how the premier exclusivity is enforced. Without an output schema, the agent lacks critical information to invoke and interpret results correctly.

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 only 25% (only 'expression' has a description). The tool description adds no information about the three undocumented parameters (region, language, max_results), leaving the agent without guidance on their meaning or use.

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 clearly states the verb 'Get' and resource 'autocomplete suggestions for a partial food search expression', and adds the 'Premier exclusive' qualifier. However, it does not explicitly distinguish this tool from siblings like search_foods, though the autocomplete nature is implied.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like search_foods, nor does it explain any conditions or prerequisites beyond the premier exclusivity.

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