Skip to main content
Glama
Sign In

ABOVO.co: Email-to-Web Publishing

by io.github.seanfenlon
OverviewDiscussionsAdmin

prepare_abovo_post

Read-onlyIdempotent

Prepare a ready-to-send email that publishes a public web page on ABOVO.co. This tool sends nothing: you or your user send the email to POST@abovo.co (or a group address) from your own email account. No login, no API key.

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": {
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "prepare_abovo_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPost content; becomes the email body.
groupNoOptional ABOVO group name; the email goes to {group}@abovo.co instead of POST@abovo.co.
formatNotext (default) or html. Mailto links carry plain text only.text
subjectYesPost title; becomes the email subject.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower, but the description adds real value beyond them: it is explicitly a non-sending preparation step, requires no login or API key, and names the destination address. The main omission is what the tool actually hands back to the caller.

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

Conciseness5/5

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

Three short sentences with the key constraint ("sends nothing") front and center; every sentence carries distinct information and nothing is padded.

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?

The tool's defining behaviour and auth posture are well covered, but with no output schema the description never says what the agent receives back (presumably a mailto link or prepared message) or how to hand it to the user, which is the natural next step for this workflow.

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 the baseline is 3, and the description adds essentially no parameter-level detail beyond schema fields. The only marginal addition is mentioning the group-address variant, which the schema already documents under the group property.

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?

States a specific verb ("Prepare") and resource ("a ready-to-send email that publishes a public web page on ABOVO.co"), and immediately scopes what it does NOT do ("sends nothing"). An agent can tell this apart from get_abovo_info without opening either schema.

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 clarifies the follow-up action (the user sends the email from their own account to POST@abovo.co) and that no auth is required, which is genuinely useful. However, it gives no explicit when-to-use/when-not guidance relative to the single sibling, and the choice between POST@abovo.co and a group address is left to the schema rather than being motivated in the description.

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

All ABOVO.co: Email-to-Web Publishing 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