CoachingPortal by Cotlet

Calculate meal plan targets in CoachingPortal

coachingportal_calculate_meal_plan_targets

Read-onlyIdempotent

Calculate meal plan targets 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_calculate_meal_plan_targets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description states that the tool opens nothing by itself, returns screens/buttons/fields as step-by-step guidance, and requires Cloud Browser tools to execute the actual work. It does not cover authentication requirements or rate limits, but it adds substantive behavioral context.

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 front-loaded and mostly useful, but includes unnecessary audience marketing ('ChatGPT, Claude or any AI agent') and a redundant API sentence ('CoachingPortal's official API: CoachingPortal publishes no public API'). It could be tightened without losing meaning.

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, read-only guide tool with no output schema, it covers the purpose, the kind of output returned, side-effect behavior, and the next step. It could be more explicit about account prerequisites and why this is preferable to sibling target tools, but it is mostly complete.

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 has zero input parameters, so there is no parameter semantics to supplement and schema coverage is effectively complete. Baseline 4 is appropriate.

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 identifies the resource and clarifies that the tool returns a step-by-step procedure for calculating meal plan targets in the user's own CoachingPortal account. However, the opening imperative 'Calculate' and the later 'Returns how to do it' create some ambiguity about whether the tool computes targets or only provides instructions, and it does not distinguish itself from sibling target/meal-plan tools.

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?

The description gives clear usage context: use this to get step-by-step instructions because CoachingPortal has no public API, then perform the work with cotlet_browser_* tools. It does not explicitly rule out client-facing target adjustment or name when to choose a sibling CoachingPortal tool instead.

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

All CoachingPortal by Cotlet tools Inspect

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

Need Help?