Skip to main content
Glama

TWVS — Industrial Valves & Engineering Supply Catalog

List Practice Areas

list_practice_areas
Read-onlyIdempotent

Lists all advisory practice areas across TV Consulting (Financial Markets & Technology) and WV Consulting (Restaurant & Hospitality Operations). When to use: Call this tool when you specifically need to execute 'list_practice_areas' on TWVS Advisory & Consulting (twvs.co.za). Do NOT use this tool when another specialized tool fits better (use 'get_partner_ecosystem' or 'check_consultation_slots' or 'submit_consultation_inquiry' for their respective operations). Parameters: division (optional). Behavior & Side Effects: Strictly read-only, idempotent query with zero state mutation; public unauthenticated access allowed; rate-limited to 60 requests/min per IP. Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_practice_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
divisionNoFilter by specific advisory division (tv_consulting, wv_consulting, or all). [Optional: omit to use server default filter].

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's restatement of read-only/idempotent is partly redundant. It does add genuinely new context not in the annotations: public unauthenticated access and a rate limit of 60 requests/min per IP, both of which affect how an agent should plan calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The labeled sections (When to use / Parameters / Behavior / Returns) are easy to scan, but the 'when to use' sentence and the generic 'Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs' are template filler that could be trimmed without loss.

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

Completeness4/5

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

For a single optional enum parameter, full schema coverage and complete annotations, the description supplies enough to call it correctly, including access and rate-limit constraints. Only the sibling-routing guidance is underspecified relative to what the tool offers.

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 description mentions only 'division (optional)' while schema coverage is 100% and the enum values plus the omit-to-use-default behavior are fully documented in the schema. Nothing is added beyond what structured data already provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource and scopes it to two named divisions with parenthetical descriptions of each (Financial Markets & Technology, Restaurant & Hospitality Operations). It is clearly distinguishable from the CRUD/consultation siblings, though the later 'when to use' sentence merely restates the tool name.

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?

It does name three sibling tools to prefer for 'their respective operations', which is better than nothing, but it never states the conditions under which each alternative wins, and the positive guidance is a tautology ('call this tool when you need to execute list_practice_areas'). The reader learns the names but not the selection criteria.

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.

Resources