mcp-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ai_api_costA | Estimate USD per request, day and month from token counts, caching and published batch discounts. Use for an API workload budget, not chat subscriptions. Model IDs use providerId/id from the bundled src/data/pricing-snapshot.json catalog. Rates are from the dated catalog snapshot returned with the result. |
| meeting_time_zonesA | Find 30-minute meeting times inside 09:00–17:00 for 2–8 people in IANA time zones. The date is local to the first person. Applies daylight saving changes; does not read calendars or send invitations. |
| recurring_scheduleA | Estimate monthly hours for weekly, biweekly and monthly tasks and return recurrence rules plus a complete RFC 5545 calendar. Use to prepare a schedule; no task is executed or calendar updated. Times float in the importing calendar’s local time zone. |
| ai_subscription_stack_costA | Total selected AI chat and coding subscriptions in USD and identify overlapping capabilities. Returns monthly charges, annual billing or twelve-charge estimates, plans and dated official sources. Use for reviewing a subscription stack, not API token costs. |
| cron_next_runsA | Preview 1–10 cron matches strictly after a supplied UTC instant within 366 days, in an IANA time zone. Supports numeric stars, lists, ranges, steps and weekday names for GitHub, Cloudflare, Quartz and AWS dialects. L, W, # and named months are rejected. This does not install or run a schedule. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: API cost estimation, subscription stack cost, meeting time zone calculation, recurring schedule estimation, and cron run preview. Descriptions explicitly differentiate the two cost tools (API vs subscriptions), and the time-related tools cover different aspects (meeting planning vs recurrence vs cron parsing). No overlap or confusion.
All names use snake_case and are noun phrases, but prefix usage is inconsistent ('ai_' on two tools, absent on others) and pluralization varies ('zones', 'schedule', 'runs'). These are minor deviations from a fully predictable pattern, yet still readable and mostly consistent.
Five tools falls within the reasonable range (3–15), but for a generically named 'mcp-tools' server the set feels under-scoped. Each tool is distinct, but the collection lacks a cohesive theme, making the count slightly low for the apparent breadth of the name.
The tools cover cost estimation and several time/schedule utilities, but they are independent with no shared domain. For a general-purpose toolkit, notable gaps exist (e.g., time zone conversion, calendar integration, broader scheduling operations), and no lifecycle coverage is present.