FavCRM

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/io.favcrm/favcrm/admin

issue_rewards

Issue a gift/reward to multiple members. Requires a gift offer ID and member IDs.

Input Schema

TableJSON Schema

Name	Required	Description
`expiresAt`	No	Optional ISO date when the reward expires
`memberIds`	Yes	Member/account IDs to receive the reward (max 50)
`giftOfferId`	Yes	The gift offer/reward scheme ID to issue

Output Schema

TableJSON 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

TDQS

A3.8/5.0

Behavior3/5

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

Annotations indicate it is not read-only and not destructive, and the description implies a write operation. However, it does not disclose additional behavioral details such as idempotency, maximum batch size, or side effects beyond the parameter descriptions.

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 a single sentence that front-loads the primary action and then lists prerequisites. No unnecessary words.

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?

Given that the tool has a simple purpose, all parameters are described in the schema, and an output schema exists, the description is adequately complete. It could mention idempotency or retry behavior for completeness.

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 the description adds no new parameter information beyond reiterating required fields. It does not elaborate on data types or defaults.

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 uses a specific verb ('issue'), specifies the resource ('gift/reward'), and indicates it applies to multiple members. This distinguishes it from sibling tools like 'earn_loyalty_points'.

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?

The description mentions prerequisites (gift offer ID and member IDs) but does not explicitly state when to use this tool vs alternatives like 'earn_loyalty_points' or other mutation tools.

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

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

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions that minimize ambiguity. Even related tools like create_post vs create_post_type are well-separated by their targets.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_account, list_services, update_post), with no mixing of naming conventions. The pattern is predictable throughout the set.

Tool Count1/5

190 tools is excessively large for any server, far exceeding the typical 3-15 tool range. The sheer volume overwhelms agents and suggests poor scoping, even for a comprehensive CRM platform.

Completeness4/5

The tool set covers CRUD operations across many domains (CRM, bookings, marketing, CMS, etc.), but notable gaps exist (e.g., no delete_account, delete_contact, update_booking). These are minor given the vast surface.

Resources

Need Help?