studio_infoAuthoritative KARVE facts — pricing & passes, first-timer info, policies (women-only, grip socks, cancellation, age), hours, location and contact. Use instead of guessing.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the 'authoritative' framing and a content list but does not disclose additional behavioral traits such as response format, data freshness, or the possibility of updates. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently covers purpose and content. It is concise and every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter, no-output-schema tool, the description adequately lists the main content areas. It could be more explicit about the response format or data currency, but the core coverage is sufficient for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters in the schema, the baseline is 4. The description appropriately says nothing about parameters since none exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides authoritative KARVE studio facts, enumerating specific categories (pricing, policies, hours, location, etc.). It distinguishes from siblings by focusing on studio-level information rather than class-specific details like class_detail or next_available.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Use instead of guessing' implies a usage context but does not explicitly mention when to use this tool versus sibling alternatives. It lacks exclusions or references to class-focused tools, so the guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear role: class_detail for specific class info, next_available for soonest openings, search_classes for full schedule, and studio_info for general facts. Slight overlap between next_available and search_classes is mitigated by distinct purposes: one finds the soonest open class, the other lists the schedule.
All names use snake_case and are readable, but the pattern is mixed: class_detail and studio_info are noun-based, next_available is adjective-based, and search_classes is verb-based. There is no consistent verb_noun pattern across the set.
Four tools is well-scoped for a read-only booking information server, covering schedule, availability, class details, and studio info without redundancy. It is within the typical 3-15 range and each tool earns its place.
The set covers core browsing needs: schedule lookup, finding available classes, getting full class details, and studio policies. It lacks actual booking or cancellation actions, but the descriptions indicate it is designed to provide information and booking links rather than handle transactions, so this is an acceptable scope.