Home / Token cost / Lodi Kids Activities

The Lodi Kids Activities MCP server costs 5,189 tokens before the first call.

Connect Lodi Kids Activities and its 72 tool definitions are loaded into the model's context on every request — 2.6% of a 200k window spent before your agent does anything.

QUICK ANSWER The Lodi Kids Activities MCP server's tool definitions consume 5,189 tokens — 2.7× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 72 tools · 5,189 tokens · 2.6% of 200k · 0.5% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 2.6%
1M WINDOW 0.5%

Corpus context: Lodi Kids Activities ranks #1011 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 5,189 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 72 tokens per tool.

ToolCategoryTokens% of server
search_daycares Read 310 6.0%
search_programs Read 277 5.3%
org_add_program_event Write 154 3.0%
org_update_program Write 154 3.0%
parent_save_program Write 152 2.9%
daycare_set_capacity Write 146 2.8%
list_upcoming_events Read 131 2.5%
daycare_respond_to_tour Read 122 2.4%
nearby_programs Read 117 2.3%
parent_request_tour Read 106 2.0%
parent_submit_review Write 103 2.0%
city_stats Read 101 1.9%
get_daycare Read 101 1.9%
parent_update_kid Write 101 1.9%
program_events_feed Write 98 1.9%
get_program Read 94 1.8%
parent_list_saves Read 93 1.8%
org_update_program_capacity Write 86 1.7%
list_reviews Read 81 1.6%
list_guides Read 79 1.5%
parent_my_upcoming_events Read 76 1.5%
parent_report_enrollment Read 76 1.5%
parent_recommended_for_me Read 72 1.4%
org_update_profile Write 72 1.4%
parent_invite_household_member Write 72 1.4%
parent_add_kid Write 71 1.4%
parent_remove_kid Destructive 69 1.3%
parent_update_prefs Write 66 1.3%
parent_unsave_program Destructive 62 1.2%
org_reply_to_review Read 62 1.2%
list_categories Read 61 1.2%
org_list_program_events Read 60 1.2%
org_cancel_program_event Destructive 59 1.1%
site_directory Read 58 1.1%
org_generate_promo_kit_url Write 58 1.1%
upcoming_registrations Read 57 1.1%
parent_calendar_subscribe_url Read 56 1.1%
admin_pending_claims Read 55 1.1%
daycare_list_tours Read 55 1.1%
get_event Read 54 1.0%
list_cities Read 54 1.0%
admin_cost_summary Read 52 1.0%
org_confirm_listing_fresh Read 51 1.0%
admin_search_trends Read 50 1.0%
org_archive_program Write 50 1.0%
parent_export_my_data Write 50 1.0%
parent_revoke_my_tokens Destructive 48 0.9%
org_analytics Read 48 0.9%
org_dashboard Read 46 0.9%
parent_leave_household Read 46 0.9%
featured_listings Read 45 0.9%
parent_accept_household_invite Write 45 0.9%
get_guide Read 43 0.8%
parent_save_daycare Write 43 0.8%
admin_live_activity Read 42 0.8%
daycare_capacity Read 42 0.8%
parent_list_kids Read 42 0.8%
parent_cancel_tour Destructive 41 0.8%
admin_pending_discoveries Read 41 0.8%
parent_my_household Read 40 0.8%
admin_mcp_stats Read 39 0.8%
daycare_list_waitlist Read 39 0.8%
parent_list_enrollments Read 39 0.8%
parent_my_waitlist_positions Read 36 0.7%
daycare_list_applications Read 35 0.7%
org_list_leads Read 33 0.6%
parent_list_tours Read 31 0.6%
parent_my_applications Read 30 0.6%
parent_me Read 29 0.6%
org_list_programs Read 28 0.5%
admin_pending_guides Read 27 0.5%
parent_my_reviews Read 27 0.5%

Most agents use a handful of these tools. They pay for all 72.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (72 tokens each).

Grant scopeDefinition costReduction
All 72 tools (no gateway) 5,189 tokens
3 granted tools ~216 tokens −96%
5 granted tools ~360 tokens −93%
10 granted tools ~721 tokens −86%

Lodi Kids Activities token-cost questions.

How many tokens does the Lodi Kids Activities MCP server use?+

Its 72 tool definitions total 5,189 tokens — 2.6% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Lodi Kids Activities consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Lodi Kids Activities's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Lodi Kids Activities to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 216 tokens, a 96% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 72 catalogued Lodi Kids Activities tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Lodi Kids Activities to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.