Skip to main content
Glama
Sign In

Rumoro

by dev.rumoro
OverviewDiscussionsAdmin

Log activity

log_activity

Logs that someone on the team contacted a person, for example by email, direct message or call. A not_contacted person moves to contacted, and a person with no owner gets the contacting member as owner. A later stage or an existing owner stays, and update_person changes them. memberId falls back to the signed-in user. Called with an API key and no memberId, it logs an activity without a member and sets no owner. Returns the new activity and the updated person.

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": {
      "channel": "<channel>",
      "id": "<id>"
    },
    "name": "log_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe aut_... id from list_people, or author.id on a mention
noteNoA short summary of what was sent or said.
channelYesHow the person was contacted.
memberIdNoThe user id of the member who reached out. Defaults to the signed-in member. With an API key and no value, the activity has no member.
occurredAtNoDefaults to now. Otherwise send the contact time as ISO 8601 or epoch ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing side effects the annotations cannot: person stage transitions, automatic owner assignment, the rule that a later stage or existing owner is preserved, and that update_person is what overrides them. Also states auth behavior (API key path) and the return payload.

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?

Four front-loaded sentences, each carrying distinct information (what it does, state effects, memberId fallback, API-key behavior, return). No filler or repetition.

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 mutating, non-idempotent tool with no output schema, the description covers the critical things: mutation side effects, ownership/stage preservation rules, auth-dependent behavior, and the return values. Nothing an agent needs before calling is missing.

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 every parameter is already documented, including the memberId fallback and occurredAt default. The description largely restates those schema-documented semantics, which is the baseline case for a fully-covered schema.

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?

Specific verb (logs) + resource (activity/contact with a person) with concrete examples (email, DM, call). It is clearly distinct from read-side siblings like list_activities and delete_activity, so an agent can route without opening the schema.

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?

Provides real situational context: the not_contacted->contacted transition, the owner-assignment rule, and the API-key-without-memberId case. It stops short of naming an alternative tool or an explicit when-not-to-use condition, but the scenario coverage is strong.

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

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