Skip to main content
Glama

foxyio

by io.usefulapi

Update subscription

foxy_update_subscription
Destructive

UPDATES a subscription — reschedule its next run (next_transaction_date), change its frequency, or activate/pause it (is_active). This MODIFIES live store data and affects future billing. Foxy hAPI: PATCH /subscriptions/{id}. Provide only the fields you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSubscription id to update.
frequencyNoBilling frequency, e.g. '1m' (monthly), '2w' (2 weeks), '1y' (yearly).
is_activeNoSet true to activate or false to pause the subscription.
next_transaction_dateNoNext run date, YYYY-MM-DD (reschedules the subscription).

Schema Changelog

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

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds meaningful context: it modifies live store data, affects future billing, uses PATCH /subscriptions/{id}, and supports partial updates. This goes beyond the annotation without contradicting it.

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 concise and front-loaded with the action and resource. It packs the endpoint, the modification semantics, the business impact, and the partial-update guidance into two efficient sentences with no filler.

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 the 4-param schema with full coverage, the destructive annotation, and the clear endpoint, the description is substantially complete for correct invocation. It lacks details about the response shape or error cases, but those are not critical for selecting and calling this update tool.

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 schema already documents all parameters. The description adds a few semantics by linking next_transaction_date to rescheduling and is_active to activate/pause, plus clarifying that only desired fields should be passed, but it doesn't heavily extend the schema.

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 states a specific verb ('UPDATES') and resource ('a subscription'), and enumerates the exact operations: rescheduling next run, changing frequency, and toggling active state. It clearly distinguishes this from the sibling foxy_update_customer and from read-only subscription tools.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool — when modifying a subscription's schedule, frequency, or active status — and includes the important guidance to provide only fields to change. It doesn't explicitly mention alternatives or when-not-to-use, but the context is clear enough.

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

All foxyio 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

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: get/list/update are clearly separated per entity (customer, subscription, transaction, etc.). The helper tools like get_default_store and get_api_home serve unique discovery purposes, and there is no overlap in their use cases.

Naming Consistency5/5

All 14 tools follow the identical pattern 'foxy_<verb>_<noun>' with verbs limited to get, list, and update. The naming is uniform, predictable, and descriptive, making it easy to infer functionality from the name alone.

Tool Count5/5

With 14 tools, the server covers a meaningful set of operations across the Foxy hAPI resources without overwhelming bloat. The count is within the ideal 3–15 range and each tool serves a clear purpose in the e-commerce domain.

Completeness3/5

The server provides robust read coverage (list/get) for most major resources (customers, subscriptions, transactions, stores, carts, coupons, items) but lacks any create or delete operations. Only customers and subscriptions support updates, leaving notable gaps for a full lifecycle (e.g., no way to create a customer or update a transaction). This is a meaningful but not severe incompleteness.

Resources