Skip to main content
Glama

Digital Manager Guru

by io.github.mcp-dir

guru_subscriptions_write_set_next_offer

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: set_next_offer]

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

C2.3/5.0
Behavior2/5

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

The description adds the useful facts that this is a flattened action and that batched execution via ids is supported, but it does not disclose what changes occur, output/error behavior, side effects, or idempotency. Since annotations already indicate a non-read-only write, the extra behavioral value added here is minimal.

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

Conciseness2/5

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

The description bloats the action list with many actions that do not represent this flattened tool; most of the list is irrelevant and could mislead an agent. It should be reduced to one sentence about set_next_offer, its data requirement, and bulk support.

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

Completeness2/5

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

With four parameters, a fully unstructured `data` object, no output schema, and minimal annotations, a complete tool description must give the caller at least the data shape and expected behavior. This description provides broad domain context but leaves the most important execution details undefined.

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

Parameters2/5

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

The schema has no parameter descriptions, so the description is obligated to explain parameter semantics, but it barely does. It says set_next_offer uses an id plus data, and that ids is for batched execution, but it never explains the structure or fields of `data` and never mentions `account`.

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

Purpose3/5

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

The description identifies Guru subscriptions as the resource and includes 'set_next_offer (id + data)' as the action, so the verb and resource are present. However, it never explains what setting a next offer means or how it differs from sibling actions like set_current_offer or change_plan; the 'Flattened action: set_next_offer' line largely restates the tool name.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus the many sibling write tools such as set_current_offer, change_plan, or add_coupon. The only practical hint is 'Bulk support: accepts ids', but no clear criteria are given for selecting this action over alternatives.

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