Skip to main content
Glama
Canada's Food Guide MCP Server

Canada's Food Guide MCP Server

Store Recipe In Temp Tables

store_recipe_in_temp_tables

Stores recipe data in temporary SQLite tables instead of virtual memory, enabling persistent recipe analysis with session-based cleanup.

Instructions

Store recipe data in temporary SQLite tables instead of virtual memory.

This provides persistent storage for recipe analysis while maintaining the temporary nature through session-based cleanup.

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": {
      "session_id": "<session_id>",
      "recipe_id": "<recipe_id>",
      "recipe_data": "<recipe_data>"
    },
    "name": "store_recipe_in_temp_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipe_idYesUnique recipe identifier
session_idYesSession identifier for data organization
recipe_dataYesComplete recipe data from get_recipe() tool

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that the tool writes to SQLite, provides persistence, and relies on session-based cleanup. However, it leaves important lifecycle behavior unclear, including whether cleanup is automatic or requires cleanup_temp_sessions, whether an existing session is required, and how duplicate recipe IDs are handled.

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?

The description is short and front-loaded with the operation, followed by one sentence explaining persistence and cleanup. Both sentences contribute useful information without repetition or unnecessary detail.

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?

Together with the fully described input schema and available output schema, the description is minimally sufficient to understand the call. Its main completeness gaps are workflow prerequisites, cleanup timing, and selection guidance among the several virtual-session, temp-session, and recipe-storage siblings.

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 the parameters already have adequate baseline documentation. The description adds a little lifecycle context for session-based organization but no further guidance on identifier formats, session prerequisites, or the expected structure of recipe_data beyond the schema's reference to get_recipe().

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, resource, and storage mechanism: storing recipe data in temporary SQLite tables. The contrast with virtual memory adds some differentiation, but it does not disambiguate the closely related sibling store_recipe_in_session.

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

Usage Guidelines4/5

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

It provides a usage context: choose persistent SQLite-backed storage for recipe analysis rather than virtual-memory storage, with session-based cleanup. It does not name concrete alternative tools, give exclusions, or explain whether create_temp_nutrition_session must be called first.

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