Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

send_member_message

Send a short note to one member of this workspace, in the name of the person the caller acts for. The member gets a notification in Onplana and an email with the note (unless they turned off all email); the email's Reply-To is the sender's address, so the member answers by replying to the email. Onplana keeps no conversation thread. Optionally attach a link to a project, or to a task in it. Recipients are active members of this workspace only, never yourself or an agent. Each call sends another email, and a sender has an hourly limit; over it the call is refused with code RATE_LIMITED. Available only while the workspace operator has turned this on.

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": {
      "recipientId": "<recipientId>",
      "text": "<text>"
    },
    "name": "send_member_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe note, 1 to 2000 characters. Blank lines separate paragraphs.
taskIdNoOptional, with projectId. A task in that project to link to instead of the project.
projectIdNoOptional. A project in this workspace to link to from the note.
recipientIdYesThe member's user id, as list_org_members returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

It discloses behavior far beyond the annotations: dual delivery (in-app notification plus email unless email is disabled), Reply-To routing so the member replies by email, no persisted thread, active-member-only recipients with self/agent exclusion, and a per-sender hourly rate limit that fails with RATE_LIMITED. It also notes the tool only works when the workspace operator enables it, and 'each call sends another email' reinforces the non-idempotent annotation.

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?

Purpose is front-loaded in the first sentence and every following sentence carries decision-relevant information (delivery, reply path, no thread, linking, recipient rules, rate limit, feature gating). It is on the long side but has no filler or repetition.

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?

With no output schema, the description still covers what the tool does, who receives it, failure mode (RATE_LIMITED) and availability gating. Minor gaps remain, such as what the call returns on success or what happens with an invalid recipientId, but an agent has enough to call it 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?

Schema coverage is 100%, so parameter definitions are already documented; the description still adds meaning by explaining that recipientId must resolve to an active member (never the caller or an agent) and that projectId/taskId are optional link attachments, with taskId scoped to a task in the linked project. That is real added semantics above the schema text.

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?

The description gives a concrete verb and resource ('Send a short note to one member of this workspace') and specifies the delivery channel (Onplana notification plus email with Reply-To), which lets an agent separate it from channel-posting siblings such as post_teams_channel_message or create_comment. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage conditions are implied rather than stated: 'Onplana keeps no conversation thread' hints that threaded discussion belongs elsewhere, and 'Recipients are active members of this workspace only, never yourself or an agent' narrows the audience. But there is no explicit when-to-use/when-not phrasing or named alternative, so an agent must infer the routing.

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

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