Wayfront

Subscription Tool

subscription-tool

Read-only

Query subscriptions. Actions: "list" — query subscriptions with filtering, sorting, pagination. "show" — get a single subscription by ID.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for "list". Default 1.
`sort`	No	Sort fields for "list". Append :asc or :desc for direction (default :asc). Example: ["created_at:desc"]. Available fields: id, user_id, number, name, status, processor_id, current_period_end, canceled_at, created_at, updated_at, deleted_at, reseller_processor_key, subscriptions.id, subscriptions.user_id, subscriptions.number, subscriptions.name, subscriptions.status, subscriptions.processor_id, subscriptions.current_period_end, subscriptions.canceled_at, subscriptions.created_at, subscriptions.updated_at, subscriptions.deleted_at, subscriptions.reseller_processor_key, invoice, user, invoices, payments, subscription_services, orders, audits, collaborators, logs.
`limit`	No	Results per page for "list". Default 20, max 100.
`action`	Yes	Action to perform.
`filters`	No	Purity filter object for "list". Keys are field names, values are operator objects. Example: {"status":{"$eq":1}}. Available fields: id, user_id, number, name, status, processor_id, current_period_end, canceled_at, created_at, updated_at, deleted_at, reseller_processor_key, subscriptions.id, subscriptions.user_id, subscriptions.number, subscriptions.name, subscriptions.status, subscriptions.processor_id, subscriptions.current_period_end, subscriptions.canceled_at, subscriptions.created_at, subscriptions.updated_at, subscriptions.deleted_at, subscriptions.reseller_processor_key, invoice, user, invoices, payments, subscription_services, orders, audits, collaborators, logs.
`subscription_id`	No	Subscription id. Required for "show" actions.

Schema Changelog

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

First observedSep 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the action breakdown (list vs show) but does not disclose additional behavioral traits such as return format, pagination details, or any side effects. It does not contradict the annotations, but the added value is modest.

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 two sentences with no redundancy. The purpose is front-loaded, and the action breakdown is immediately useful. Every word earns its place, making it an exemplar of conciseness.

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

Completeness3/5

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

Given the tool has six parameters and nested objects but no output schema, the description is adequate but thin. It does not describe the response shape, pagination behavior beyond schema defaults, or any constraints on usage. The schema covers parameter details, but the description leaves return-value expectations implicit, which is acceptable for a read-only tool but not fully complete.

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?

The input schema has 100% description coverage, including detailed parameter explanations (e.g., sort fields, filters object example, defaults). The description adds no parameter-specific meaning beyond what the schema already provides, so it meets the baseline for full schema coverage.

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 clearly states the verb 'query' with the resource 'subscriptions' and distinguishes the two actions: 'list' for filtered/sorted/paginated queries and 'show' for a single subscription by ID. This is specific and unambiguous, leaving no doubt about what the tool does.

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?

The description implies usage through the action names: use 'list' for multiple subscriptions with filtering, 'show' for one by ID. However, it does not explicitly state when to use this tool over alternatives or provide exclusions. Since it is the only subscription-specific tool among siblings, the context is clear, but the guidance is not explicit.

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

All Wayfront tools Inspect

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.

Resources

Need Help?