Skip to main content
Glama

Digital Manager Guru

by io.github.mcp-dir

guru_subscriptions_write_remove_increment_discount

Mutações em assinaturas Guru. Ações: cancel (id, +data opcional); cancel_at_cycle_end (id); add_coupon (id + data); remove_coupon (id); set_current_offer (id + data); set_next_offer (id + data); set_cycle_end_date (id + data); set_trial_end_date (id + data); set_installment (id + data); change_plan (id + data); simulate_plan (id + data); set_payment_types (id + data); set_increment_discount (id + data); remove_increment_discount (id).

[Flattened action: remove_increment_discount]

Bulk support: accepts ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
idsNo
dataNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

D1/5.0
Behavior1/5

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

The description does not disclose side effects, authorization requirements, rate limits, or whether the operation is destructive. Annotations indicate non-read-only, but no behavioral details are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and lists numerous unrelated actions, which dilutes clarity. It is not concise and fails to focus on the specific operation (remove_increment_discount).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool is named for a specific action, the description is incomplete. It does not explain what removing an increment discount entails, expected input/output, or how it differs from other actions. The description is insufficient for correct tool invocation.

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

Parameters1/5

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

The schema defines parameters (id, ids, data, account) without any descriptions. The description does not explain what these parameters represent or their expected values, leaving the agent without necessary guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists multiple subscription mutations without clearly specifying that this tool is specifically for removing increment discounts. The name and 'flattened action' hint at this, but the description does not explicitly state the tool's primary purpose, making it ambiguous and potentially misleading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the many similar subscription write tools (e.g., add_coupon, set_increment_discount). The description lacks context on selection criteria or prerequisites.

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

All Digital Manager Guru 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

C2.3/5.0
Disambiguation3/5

The tool names themselves are distinct (e.g., guru_subscriptions_get vs guru_subscriptions_activities), but the descriptions for each resource are identical except for a '[Flattened action: X]' tag, listing all possible actions. This repetition can confuse agents into selecting the wrong tool, especially since many tools share the same description body. The naming is clear but the descriptive overlap undermines disambiguation.

Naming Consistency4/5

The majority of tools follow a consistent pattern: guru_<resource>_<action> for reads and guru_<resource>_write_<action> for writes. However, there are outliers like 'authenticate', 'connect', 'marketplace', 'report_bug', etc., which break the pattern. Within the Guru API itself, the naming is highly predictable, but the occasional non-Guru tool reduces overall consistency.

Tool Count1/5

With 101 tools, the server is grossly over-scoped. The API has been fragmented into a separate tool for every action across many resources (e.g., subscriptions alone have 15+ tools). This is far beyond the typical MCP server size and makes the tool list overwhelming and impractical for agents to navigate. The extreme granularity offers no benefit over a smaller, well-organized set.

Completeness4/5

The tool set covers a wide range of operations: CRUD for contacts, subscriptions, transactions, products, coupons, webhooks, and more, including write actions like refunds, chargebacks, and subscription modifications. The domain appears well-covered, though some resources lack create operations (e.g., no create subscription) and there are a few gaps like missing explicit update for transactions. Overall, the coverage is thorough for the stated API surface.

Resources