Skip to main content
Glama

CoachingPortal by Cotlet

Import food to plan in CoachingPortal

coachingportal_import_food_to_plan
Read-onlyIdempotent

Import food to plan in the user's own CoachingPortal account from ChatGPT, Claude or any AI agent. Returns how to do it in CoachingPortal step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser. CoachingPortal's official API: CoachingPortal publishes no public API.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds the crucial fact that the tool 'opens nothing by itself' and merely returns guidance rather than mutating anything. It also explains why browser automation is required (no public API), which prevents the agent from expecting a server-side write. The residual gap is that it doesn't say what the returned instructions look like in structure or length.

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?

Front-loaded with the purpose and the important 'opens nothing' caveat, which is good. The trailing clause 'CoachingPortal's official API: CoachingPortal publishes no public API.' is a redundant, awkward fragment that could be a single clean phrase, and the sentence packing makes the description denser than necessary.

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 zero-parameter, no-output-schema tool, the description covers the essentials: what it returns, that it has no side effects, why an API route isn't available, and which tool family continues the workflow. It stops short of describing the return payload's shape or any prerequisites for the Cloud Browser step.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; baseline applies. The description correctly implies all context (which plan, which food) is gathered later via the browser tools rather than through arguments.

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?

Names a specific verb and resource (import food to plan) and immediately clarifies the actual output: step-by-step instructions for screens, buttons and fields. The opening phrasing sounds like it performs the import, but the description corrects that within the same sentence, so an agent can tell what it gets back. It does not name the closest sibling (e.g. manage_personal_food_log or edit_meal_plan) as an alternative.

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?

States the follow-up path clearly: use the cotlet_browser_* tools in the user's Cloud Browser after reading the steps. However, it never says when this tool is the right choice versus a direct CoachingPortal plan/log tool, so the agent must infer the selection condition from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources