Skip to main content
Glama

Digital Manager Guru

by io.github.mcp-dir

guru_subscriptions_write_set_cycle_end_date

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_cycle_end_date]

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description does not contradict these. The description adds the useful context that bulk execution via ids is supported, but it does not disclose what happens when the cycle end date is changed, whether it affects the current billing period, or what side effects may occur. Still, the core write/non-destructive behavior is covered by annotations, so a middle score is appropriate.

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 is a bloated generic template that lists every subscription mutation action, most of which are irrelevant to this specific tool. The relevant action is buried behind 13 unrelated actions, and the description is not front-loaded or tailored to this tool. The bulk-support sentence is the only concise, tool-specific addition.

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?

This is a write tool with an unstructured `data` object and no output schema, so the description should explain what setting the cycle end date does, what keys are expected in `data`, and what response/errors to expect. It does none of that. The bulk-support hint is a small positive, but overall the description is inadequate for an agent to invoke this tool correctly.

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 input schema has 0% coverage, so the description must compensate. It indicates 'set_cycle_end_date (id + data)' and mentions bulk support, which adds some meaning to the ids parameter. However, it does not explain the structure or required fields of the free-form `data` object, and it implies data is required while the schema only requires `id`, creating potential confusion.

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

Purpose2/5

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

The description opens with a generic statement about Guru subscription mutations and lists 14 possible actions. The tool is identified only by the line '[Flattened action: set_cycle_end_date]', which merely restates the action portion of the name and does not explain that this tool changes the billing cycle end date. It does not clearly distinguish this tool from siblings like guru_subscriptions_write_set_trial_end_date.

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?

No guidance is given about when to use this tool versus the many sibling mutation tools. The long list of actions implies that alternatives exist, but there is no explanation of when set_cycle_end_date is appropriate, no prerequisites, and no exclusions. The only operational hint is the bulk-support note about accepting ids.

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