Skip to main content
Glama

CoachingPortal by Cotlet

Manage personal food log in CoachingPortal

coachingportal_manage_personal_food_log
Read-onlyIdempotent

Manage personal food log 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_manage_personal_food_log"
  }
}

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description is not carrying the safety burden alone. It nonetheless adds genuinely useful behavior: the tool opens nothing by itself, returns instructional content rather than mutating anything, and CoachingPortal has no public API — which explains why browser tools are required. It stops short of describing the shape or length of the returned instructions.

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 core point (returns step-by-step instructions, opens nothing, use browser tools afterward) is front-loaded and useful. But 'from ChatGPT, Claude or any AI agent' is filler, and repeated branding ('CoachingPortal' appears five times) makes three sentences do the work of two.

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 instructional tool with no output schema, the description covers what it returns, what it does not do, and the required follow-up tooling. The only missing piece is a sense of how the returned steps are structured or scoped (whole log vs. single entry).

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 the baseline is 4; there is no parameter semantics to compensate for. The description correctly implies the call needs no arguments because the user context and target are implied by the tool scope.

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 states a specific resource (the user's personal food log in CoachingPortal) and, importantly, clarifies what the tool actually returns: step-by-step instructions with screens, buttons and fields rather than performing the action. That distinction is clear. It does not differentiate from similar siblings such as coachingportal_manage_personal_workout or coachingportal_log_personal_progress, which appear to follow the same instructional pattern.

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?

It gives a concrete follow-up workflow: call this, then execute the steps with the cotlet_browser_* tools in the user's Cloud Browser. However, there is no guidance on when to choose this tool over closely named siblings (e.g. logging progress vs. managing a food log) and no when-not conditions.

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