Skip to main content
Glama

Mob (Demo)

by io.github.benkaiser

life_event_manage

Create, list, update, delete, or restore life events for a contact. • action="create": Record a new life event. Requires contact_id, event_type, and title. Optional description, occurred_at, related_contact_ids. • action="list": List life events for a contact. Requires contact_id. Optional page, per_page, include_deleted. • action="update": Update a life event. Requires id. Optional event_type, title, description, occurred_at, related_contact_ids. • action="delete": Soft-delete a life event. Requires id. • action="restore": Restore a soft-deleted life event. Requires id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe life event ID (required for "update", "delete", "restore")
pageNoPage number for "list" (default: 1)
titleNoTitle (e.g. "Started at Google", "Moved to Berlin") - required for "create", optional for "update"
actionYesAction to perform
per_pageNoResults per page for "list" (default: 20)
contact_idNoThe contact ID (required for "create" and "list")
event_typeNoEvent type (e.g. "new_job", "got_married", "moved") - required for "create", optional for "update"
descriptionNoDescription (optional for "create" and "update")
occurred_atNoWhen it happened (ISO date, optional for "create" and "update")
include_deletedNoInclude soft-deleted life events in "list" results (default: false)
related_contact_idsNoIDs of other contacts involved (optional for "create" and "update")

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly mentions 'Soft-delete' for delete and 'Restore a soft-deleted life event' for restore, and the list action documents include_deleted. It does not discuss permissions, side effects, or return values, but the soft-delete semantics are a key behavior disclosed beyond simple CRUD.

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?

The description is front-loaded with the main purpose, followed by succinct, bullet-style action breakdowns. Each sentence earns its place, and the structure allows quick scanning of all five actions and their parameter requirements without unnecessary verbosity.

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 complex multi-action tool with no output schema, the description covers all input parameters and per-action requirements, including soft-delete behavior. It does not explain return values or error conditions, which could be a gap, but the overall input-side guidance is comprehensive enough for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds significant value by grouping parameters per action and stating requirements (e.g., 'Requires contact_id, event_type, and title' for create). This clarifies parameter combinations that the schema alone does not explicitly define, making tool invocation much more straightforward.

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 opens with 'Create, list, update, delete, or restore life events for a contact,' which uses a specific verb set and clearly identifies the resource (life events). This distinguishes it from sibling tools like activity_manage or note_manage, which handle different entities.

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?

The description provides action-specific guidance, stating exactly which parameters are required for each action. It implicitly communicates when to use the tool (for life event management) and differentiates from siblings by resource type. It does not explicitly name alternatives or exclusions, but the context is clear.

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

All Mob (Demo) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools are clearly distinct by entity, but contact_get and contact_timeline overlap significantly, and debt_manage's action='list' duplicates what other entities do with a dedicated list tool. Descriptions are detailed enough to resolve most ambiguity, though.

Naming Consistency3/5

Tool names are mostly snake_case and readable, but they mix conventions: noun_verb (contact_create), verb_noun (batch_create_activities), and descriptive phrases (contacts_needing_attention). The noun_manage pattern is dominant, but the lack of uniformity makes the naming less predictable.

Tool Count2/5

With 42 tools, the surface is very large, even for a full-featured CRM. Many tools bundle multiple actions, but the sheer number forces an agent to consider many options, increasing selection difficulty and cognitive load.

Completeness5/5

The server provides comprehensive CRM coverage: contacts, activities, notes, tasks, reminders, gifts, debts, relationships, tags, custom fields, notifications, settings, and exports. It supports batch operations, duplicate detection, merge, and special queries, leaving few if any obvious gaps.

Resources