Skip to main content
Glama

foxyio

by io.usefulapi

List subscriptions

foxy_list_subscriptions
Read-only

List a store's subscriptions (recurring orders). Returns a HAL collection embedding fx:subscriptions. Foxy hAPI: GET /stores/{store_id}/subscriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoomNoComma-separated related resources to embed, e.g. 'transaction_template,last_transaction'.
limitNoMax results per page (Foxy default 20).
offsetNoPagination offset.
store_idNoStore id. If omitted, the default store (fx:store) is used.
is_activeNoFilter to active (true) or inactive (false) subscriptions.

Schema Changelog

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

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint true; the description adds that it returns a HAL collection embedding fx:subscriptions and uses GET, confirming no side effects and disclosing response shape. It doesn't cover pagination behavior beyond params, but that's minor.

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?

Single sentence front-loads action and resource, then supplies return format and endpoint; 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?

For a simple list tool with no required params and full schema coverage, the description gives the key context (store-scoped collection, HAL format, GET endpoint). It doesn't explicitly mention pagination or default store, but those are in the schema, so nothing critical is missing.

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 fully documents all five optional parameters. The description adds no parameter-specific meaning, which is acceptable at baseline.

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?

States the verb 'List' and resource 'a store's subscriptions' with clarifying 'recurring orders,' distinguishing it from foxy_get_subscription and foxy_update_subscription. Also names the exact endpoint and return collection rel.

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?

Usage is implied by the list vs. resource-scoped name, and the endpoint clarifies it is a collection read. However, it does not explicitly say when to prefer foxy_get_subscription for a single subscription or exclude update scenarios, so an agent must infer the fit.

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