Skip to main content
Glama
Sign In

Angi 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 Angi it covers these actions: List leads, Message a homeowner, Set lead status, Request lead credit, List reviews, Reply to review, Request homeowner review, Update service locations.

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: Angi.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, it discloses that the call is free, starts no browser session, and falls back to general guidance for uncatalogued apps. It also previews the guidance contents, though it could more explicitly state that the call only returns guidance and never performs the listed app actions itself.

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 purpose is front-loaded, and the invocation timing, fallback behavior, cost, and session behavior are all expressed efficiently. The opening sentence is dense and the closing Angi action list makes the description somewhat long, but the information remains relevant.

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 two-optional-parameter guidance tool without an output schema, the description supplies the expected guidance contents, invocation point, app coverage, fallback behavior, and session and cost characteristics. Together with the fully documented schema and safety annotations, it provides what an agent needs to select and invoke the tool correctly.

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 schema already fully documents both optional parameters, including the Angi default and the task wording. The description adds useful semantics for `app` by explaining that uncatalogued web apps are accepted and receive general guidance, while the Angi action list gives concrete examples of supported tasks.

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 clearly identifies this as a tool for obtaining app-operating guidance, including browser selection, sign-in, steps, screens, menus, actions, and relevant dedicated tools. Its references to subsequent browser work and dedicated tools distinguish it from the siblings that execute browser or Angi actions.

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?

The explicit instruction to call it "before the first browser step in an app" provides a clear invocation point. It also explains that any web app is supported, that uncatalogued apps receive the general method, and which Angi tasks have specific coverage.

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

All Angi 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