FavCRM

search_members

Read-onlyIdempotent

Search and filter members/accounts. Supports text search, date ranges, booking/activity history, membership tier, tags, and more. Use lastBookingBefore/inactiveDays to find inactive members.

Input Schema

Name	Required	Description
`sort`	No	Sort column: name, email, or createdAt
`limit`	No	Max results (default 20)
`order`	No	Sort order
`search`	No	Name, email, or phone to search
`source`	No	Filter by account source
`tagIds`	No	Filter by tag IDs
`tierId`	No	Filter by membership tier ID
`lifeStage`	No	Filter by life stage
`hasBooking`	No	Filter to members with/without any booking
`createdAfter`	No	ISO date — accounts created after this date
`inactiveDays`	No	Members with no activity in the last N days
`createdBefore`	No	ISO date — accounts created before this date
`hasMembership`	No	Filter to members with active membership
`lastBookingAfter`	No	ISO date — members who have a booking after this date
`membershipStatus`	No	Filter by membership status
`lastActivityAfter`	No	ISO date — members with activity after this date
`lastBookingBefore`	No	ISO date — members whose last booking is before this date (or have no bookings)
`lastActivityBefore`	No	ISO date — members with no activity since this date

Output Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / lifeStage / enum

Previous value: -[
-  "lead",
-  "active",
-  "churned",
-  "vip"
-]New value: +[
+  "lead",
+  "active",
+  "churned",
+  "vip",
+  "prospect"
+]

First observedJun 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the notable behavioral fact that lastBookingBefore also matches members with no bookings at all, but says nothing about result caps, pagination, or default ordering beyond what the schema states.

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 tight sentences with the core purpose front-loaded, followed by capability breadth and a high-value use case. No filler or repetition, and it stays readable despite an 18-parameter surface.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Combined with a fully documented schema, the description supplies enough context to invoke the tool correctly, though the lack of sibling routing is the remaining gap.

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% with 18 self-documented parameters, so the schema carries parameter meaning. The description only highlights the inactive-member filters, which the schema already documents, adding no syntax or interaction guidance (e.g., how inactiveDays combines with lastActivityBefore).

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?

States a specific verb+resource ('Search and filter members/accounts') and enumerates the filter surface. It does not differentiate from nearby siblings such as list_contacts, get_member_profile, or get_segment_members, so an agent must infer which member-listing tool to pick.

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?

Offers one concrete scenario ('Use lastBookingBefore/inactiveDays to find inactive members'), which is useful task framing. However it names no alternatives or exclusions, and never says when a different member-retrieval tool is preferable.

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

All FavCRM tools Inspect

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.