Skip to main content
Glama
Sign In

GlossGenius MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: how to work in an app

cotlet_app_guide
Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For GlossGenius it covers these actions: List appointments, Book appointment, Reschedule appointment, Find client, Get sales summary.

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

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: GlossGenius.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful non-annotated behavior: it is free, starts no browser session, works generically outside the catalog, and surfaces dedicated tools when available. It stops short of describing the exact response structure, but that is a minor gap given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and most sentences earn their place by clarifying scope, timing, cost, and coverage. It is somewhat run-on and could be split into shorter statements, but it remains readable and purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-optional-parameter guide-retrieval tool with no output schema, the description supplies what an agent needs: what the tool returns, when to call it, what happens for uncatalogued apps, and what GlossGenius coverage includes. No critical decision or invocation context is missing.

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 both parameters are already documented. The description adds only modest meaning beyond that, mainly clarifying that the app parameter can refer to any web app and that outside-catalog apps receive the general method. It does not materially enrich the task parameter beyond what the schema already says.

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

Purpose5/5

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

The description states a specific resource and task: guidance for working in an app through Cotlet's Cloud Browser tools. It enumerates what the guidance covers (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools) and clearly differentiates itself from the browser-action siblings by positioning itself as the prerequisite guide.

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

Usage Guidelines5/5

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

It gives an explicit usage rule: "Call it before the first browser step in an app." It also clarifies scope (any web app; outside-catalog apps get the general method) and notes that for GlossGenius it covers specific actions, which helps an agent route correctly.

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

All GlossGenius MCP Server and API by Cotlet toolsInspect
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