Skip to main content
Glama

Mob (Demo)

by io.github.benkaiser

note_list

List and search notes. When contact_id is provided alone, lists that contact's notes (pinned first). Add query, tag_name, is_pinned, or omit contact_id to search across all contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
queryNoSearch term matched against note title and body
sort_byNoSort field (default: updated_at)
per_pageNoResults per page (default: 20)
tag_nameNoFilter to notes belonging to contacts with this tag
is_pinnedNoFilter by pinned status
contact_idNoFilter by contact ID (optional - omit to search across all contacts)
sort_orderNoSort direction (default: desc)
include_deletedNoInclude soft-deleted notes in results (default: false)

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds meaningful behavior beyond the schema: pinned-first ordering and the subtle mode switch when additional filters are added. It omits details like include_deleted behavior, but those are present in the schema.

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?

Two sentences, front-loaded with the core purpose, and every word earns its place. No fluff or repetition of schema details.

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 9-parameter list tool with no output schema and no annotations, the description covers the essential behavioral modes and search semantics. Pagination and sort defaults are left to the schema, which is acceptable, though return format is not described.

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 baseline is 3. The description adds semantics for contact_id, clarifying that it only applies when used alone, and explains that query/tag_name/is_pinned shift to global search. This goes beyond schema descriptions.

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 clearly states the tool 'List and search notes' with a specific verb and resource. It also distinguishes two behavioral modes (contact-specific vs global search) and naturally differentiates from sibling tools like note_manage.

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 clear context on parameter combinations: contact_id alone lists that contact's notes; adding query, tag_name, is_pinned, or omitting contact_id searches across all contacts. It does not explicitly name alternatives or exclusions, hence not a 5.

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