Skip to main content
Glama

CoachingPortal by Cotlet

Favorite food in CoachingPortal

coachingportal_favorite_food
Read-onlyIdempotent

Favorite food 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_favorite_food"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description adds real behavioral detail: the return value is step-by-step screens/buttons/fields, and the tool has no side effects ('opens nothing by itself') and requires a follow-up browser action. This meaningfully elaborates on readOnlyHint=true and destructiveHint=false. It does not cover failure modes or what happens if no browser session exists, so it falls short of a 5.

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 critical fact — that this returns instructions rather than performing the action — is buried mid-sentence rather than front-loaded. The clause 'from ChatGPT, Claude or any AI agent' and the trailing 'CoachingPortal's official API: CoachingPortal publishes no public API' are redundant and could be cut without losing meaning.

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?

For a zero-parameter, no-output-schema guidance tool, the description does explain what comes back (step-by-step screens and fields) and how to act on it. What is missing is the scope of the underlying task itself, so an agent cannot confidently decide this is the right guide before calling it.

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 and the schema is closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns step-by-step guidance for a CoachingPortal task, which is a concrete resource, but the action itself ('favorite food') is never defined — an agent cannot tell whether this means setting a favorite food, viewing it, or something in a food log. It also never distinguishes itself from the many food-related siblings such as coachingportal_search_food_library or coachingportal_import_food_to_plan.

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?

The description does establish the usage pattern implicitly: this tool only returns instructions and 'opens nothing by itself', and the actual work must then be done via cotlet_browser_* tools in the Cloud Browser. That is useful routing, but there is no explicit when-to-use versus when-not, and no guidance on which sibling to pick for related account tasks.

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