evo_get_member_count
Read-onlyIdempotent
Count of active members (drives the billing tier). Returns { active, total }.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No |
EVO Academia
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds value by specifying the return structure ({ active, total }) and clarifying the 'active' filter, which goes beyond annotations. It does not add error or pagination details, but given the simple read-only nature, this is sufficient.
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 a single, front-loaded sentence that efficiently conveys purpose and return shape without any fluff. Every word adds value.
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?
The tool is simple and the return shape is given, but the unexplained parameter leaves a significant hole. For a one-parameter read-only tool, the description should at least hint at what 'account' means. Without it, the description is not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not mention the 'account' parameter at all. With 0% schema description coverage, the agent has no idea what 'account' refers to, making it impossible to correctly invoke the tool. This is a critical gap.
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 tool's function: counting active members, and ties it to billing tier, distinguishing it from sibling tools like evo_member_list and evo_member_get. The return shape is also specified.
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 use for billing-related queries ('drives the billing tier') but does not explicitly state when to use this over alternatives or provide exclusions. It offers context but no clear guidance on selecting this tool among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation1/5
Several tools are duplicated with nearly identical descriptions, distinguished only by a '[Flattened action]' footnote (e.g. evo_activity_list vs. evo_activity_schedule, evo_member_get vs. evo_member_list, evo_prospect_write_create vs. evo_prospect_write_update). An agent would struggle to pick the correct one without parsing fine-print labels. authenticate and connect also blur the auth boundary.
Naming Consistency2/5
The EVO tools use a rough 'evo_<noun>_<action>' pattern but mix verb positions and styles: evo_member_get, evo_list_accounts, evo_activity_schedule, evo_sales_create, evo_bank_accounts. Platform tools like authenticate, connect, report_bug, and marketplace abandon the evo_ prefix entirely, and the giant marketplace tool follows no naming convention.
Tool Count2/5
26 tools is above the 15–25 'heavy' band, and several are redundant flattened variations that should be merged. The set also mixes domain-specific EVO tools with unrelated platform utilities (marketplace, toolkit_info, report_bug), inflating the count without coherent coverage.
Completeness2/5
The domain is gym management (members, activities, prospects, sales, receivables), but the surface has major gaps: no member create/update/delete, no activity-create or schedule management, and only partial write operations elsewhere. Some tools contain unresolved 'PROBE' prompts, indicating unfinished endpoints that agents cannot reliably use.