Skip to main content
Glama
Sign In

Cosend

by app.cosend
OverviewDiscussionsAdmin

Browse and fill in automation recipes

automation_recipes
Read-onlyIdempotent

Works with the recipe library. action list returns the published recipes as cards, one page at a time. action instantiate fills one recipe in with params and returns the automation document (ir) with its validation report; it writes nothing, so saving the document is a separate step. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "automation_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoThe recipe’s slug, from the recipe list.
afterNoThe next_cursor of the previous page, to read the page after it. Omit for the first page.
limitNoHow many records to return. Defaults to 25, maximum 100.
actionYeslist for the recipe library; instantiate to turn one recipe, named by slug, with its params, into an automation document.
paramsNo
connection_idNoFor action list: marks the recipes that cannot work on this number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world. Description reinforces read-only and adds the non-obvious behavior that instantiate writes nothing and saving is a separate step, plus that list paginates. It does not discuss permissions or rate limits, so 4.

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?

Four short sentences organized as overview then per-action behavior. The opening 'Works with the recipe library' is slightly vague but the rest is front-loaded and waste-free.

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 six-parameter, nested-param, no-output-schema tool, it describes both return forms (cards and automation document plus validation report) and pagination. It does not explain the nested params object, but overall enough to invoke correctly.

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 coverage is 83%, above the baseline where schema handles parameter documentation. The description explains what action list and instantiate do but adds little about slug, after, limit, connection_id, or the nested params object beyond the schema. Baseline 3.

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?

States specific operations: list returns published recipes as cards one page at a time; instantiate fills a recipe and returns an automation document with validation report. The resource is clear. It does not name sibling automation tools, so 4.

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

Usage Guidelines4/5

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

Clearly distinguishes the list action from instantiate and signals instantiate is a preview/validation step before saving. No explicit guidance on when to choose this over get_automation_catalogue or list_automations, but action-level usage is clear.

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

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