Skip to main content
Glama

Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: sign the user up and request access

cotlet_request_access

Creates the user's Cotlet account and submits their access request for the apps they need, no key needed. Use only when the user asks you to sign them up. Only when the user asks you to: create their Cotlet account and request access for them. Never sign anyone up on your own initiative. Ask the user for every value: their email, which apps they want, what you will do with them. Do not guess or invent any of it. Ask for a password. If the user leaves it to you, generate a random one of at least 20 characters, then show it to them after sign-up together with the email. Show the user everything you will send, get their OK, then send it with user_confirmed: true. One call creates the account and submits the access request. Limit: 10 sign-ups an hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe user's name, if they give it.
roleNoWhat best describes the user.
emailYesThe user's own email. Ask the user; never invent one.
sourceNoWhere the user heard about Cotlet, if they say.
passwordYesPassword for the user's new Cotlet account. Ask the user; if they leave it to you, generate a random one of at least 20 characters and show it to them once the account is created.
use_caseNoWhat the agent will do for the user with these apps, in their words.
agent_nameYesYour own name as an agent, e.g. "Claude Code" or "ChatGPT".
integrationsNoSlugs of the catalog apps the user wants (GET /api/v1/apps lists them).
user_confirmedYestrue only after the user asked for this account and approved every value above. Never sign anyone up on your own initiative.
custom_integrationsNoApps the user wants that are not in the catalog, by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / integrations / items / enum
      Previous value: -[
-  "acculynx",
-  "acumatica",
-  "airalo",
-  "alegra",
-  "bandcamp",
-  "bandsintown",
-  "bark",
-  "bayut",
-  "beautiful-ai",
-  "bokio",
-  "bookingkoala",
-  "booksy",
-  "buildertrend",
-  "chargebee",
-  "civitatis",
-  "clockshark",
-  "contractor-foreman",
-  "crexi",
-  "daysmart",
-  "dext",
-  "dice",
-  "doorloop",
-  "dribbble",
-  "dubsado",
-  "e-boekhouden",
-  "e-conomic",
-  "erpnext",
-  "everfit",
-  "evite",
-  "exact-online",
-  "expensify",
-  "facturama",
-  "faire",
-  "fakturownia",
-  "fatture-in-cloud",
-  "fiken",
-  "fitatu",
-  "fortnox",
-  "fresha",
-  "getyourguide",
-  "glossgenius",
-  "hemnet",
-  "hipcamp",
-  "holded",
-  "hostelworld",
-  "housecall-pro",
-  "houzz-pro",
-  "idealista",
-  "ifirma",
-  "immobiliare",
-  "invoice-ninja",
-  "jobber",
-  "joist",
-  "joy",
-  "kickserv",
-  "kiwi-com",
-  "klook",
-  "knowify",
-  "lexware-office",
-  "libsyn",
-  "little-hotelier",
-  "mangomint",
-  "mariana-tek",
-  "marketsharp",
-  "mashvisor",
-  "medium",
-  "meetup",
-  "meevo",
-  "milanote",
-  "momence",
-  "myob",
-  "nextdoor",
-  "odoo",
-  "omio",
-  "paperless-post",
-  "partiful",
-  "patreon",
-  "payhip",
-  "peerspace",
-  "pennylane",
-  "peopleperhour",
-  "perfect-venue",
-  "pirate-ship",
-  "pixieset",
-  "polarsteps",
-  "procountor",
-  "property-finder",
-  "pushpress",
-  "quora",
-  "recurly",
-  "rent-manager",
-  "rently",
-  "resimpli",
-  "riverside",
-  "service-autopilot",
-  "service-fusion",
-  "setmore",
-  "sevdesk",
-  "signupgenius",
-  "siteminder",
-  "skool",
-  "snelstart",
-  "soundcloud",
-  "substack",
-  "suitedash",
-  "systeme-io",
-  "szamlazz-hu",
-  "taxdome",
-  "teachable",
-  "teachers-pay-teachers",
-  "thrivecart",
-  "thryv",
-  "thumbtack",
-  "tiqets",
-  "tradify",
-  "trainerize",
-  "truecoach",
-  "udemy",
-  "uscreen",
-  "vagaro",
-  "wanderlog",
-  "whova",
-  "workiz",
-  "yardbook",
-  "zen-planner",
-  "zenmaid",
-  "zola",
-  "zoopla"
-]New value: +[
+  "acculynx",
+  "acumatica",
+  "airalo",
+  "alegra",
+  "bandcamp",
+  "bandsintown",
+  "bark",
+  "bayut",
+  "beautiful-ai",
+  "bokio",
+  "bookingkoala",
+  "booksy",
+  "buildertrend",
+  "chargebee",
+  "civitatis",
+  "clockshark",
+  "contractor-foreman",
+  "crexi",
+  "daysmart",
+  "dext",
+  "dice",
+  "doorloop",
+  "dribbble",
+  "dubsado",
+  "e-boekhouden",
+  "e-conomic",
+  "erpnext",
+  "everfit",
+  "evite",
+  "exact-online",
+  "expensify",
+  "facturama",
+  "faire",
+  "fakturownia",
+  "fatture-in-cloud",
+  "fiken",
+  "fitatu",
+  "fortnox",
+  "fresha",
+  "getyourguide",
+  "glossgenius",
+  "google-search-console",
+  "hemnet",
+  "hipcamp",
+  "holded",
+  "hostelworld",
+  "housecall-pro",
+  "houzz-pro",
+  "idealista",
+  "ifirma",
+  "immobiliare",
+  "invoice-ninja",
+  "jobber",
+  "joist",
+  "joy",
+  "kickserv",
+  "kiwi-com",
+  "klook",
+  "knowify",
+  "lexware-office",
+  "libsyn",
+  "little-hotelier",
+  "mangomint",
+  "mariana-tek",
+  "marketsharp",
+  "mashvisor",
+  "medium",
+  "meetup",
+  "meevo",
+  "milanote",
+  "momence",
+  "myob",
+  "nextdoor",
+  "odoo",
+  "omio",
+  "paperless-post",
+  "partiful",
+  "patreon",
+  "payhip",
+  "peerspace",
+  "pennylane",
+  "peopleperhour",
+  "perfect-venue",
+  "pirate-ship",
+  "pixieset",
+  "polarsteps",
+  "procountor",
+  "property-finder",
+  "pushpress",
+  "quora",
+  "recurly",
+  "rent-manager",
+  "rently",
+  "resimpli",
+  "riverside",
+  "service-autopilot",
+  "service-fusion",
+  "setmore",
+  "sevdesk",
+  "signupgenius",
+  "siteminder",
+  "skool",
+  "snelstart",
+  "soundcloud",
+  "substack",
+  "suitedash",
+  "systeme-io",
+  "szamlazz-hu",
+  "taxdome",
+  "teachable",
+  "teachers-pay-teachers",
+  "thrivecart",
+  "thryv",
+  "thumbtack",
+  "tiqets",
+  "tradify",
+  "trainerize",
+  "truecoach",
+  "udemy",
+  "uscreen",
+  "vagaro",
+  "wanderlog",
+  "whova",
+  "workiz",
+  "yardbook",
+  "zen-planner",
+  "zenmaid",
+  "zola",
+  "zoopla"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds behavior the annotations don't convey: one call does both account creation and access submission, a rate limit of 10 sign-ups/hour, and a password-generation fallback with a rule to display the generated password and email afterward. These are concrete operational traits beyond the openWorld/destructive hints.

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?

There is significant redundancy: 'Use only when the user asks you to sign them up' is immediately restated as 'Only when the user asks you to: create their Cotlet account and request access for them.' The confirmation and password rules are front-loaded and clear, but the repetition of the same instruction three times costs it.

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 10-parameter mutation with no output schema, it covers the required workflow (collect values, confirm, call once) and the verification step. It does not explain what the access-request submission returns or what happens on partial failure, but the schema carries the field documentation.

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?

Schema coverage is 100%, so baseline is 3. The description adds process semantics the schema does not: ask for every value rather than guessing, ask for a password, and only send once the user approves with user_confirmed: true. That elevates it above the schema baseline.

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 compound action: creating the user's Cotlet account and submitting their access request. The title adds scope ('sign the user up'), and no sibling tool does anything similar, so it is unambiguous.

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?

Explicit when-to-use ('Use only when the user asks you to sign them up') and a clear prohibition ('Never sign anyone up on your own initiative'), plus the required confirmation step. This is the strongest part of the definition.

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

All Cotlet toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources