Skip to main content
Glama

TWVS — Industrial Valves & Engineering Supply Catalog

Check Consultation Slots

check_consultation_slots
Read-onlyIdempotent

Retrieves current advisory consultation availability, lead times, and scheduling channels for Sandton, Johannesburg, Pretoria, Cape Town, Durban, SADC, and global remote engagements. When to use: Call this tool when you specifically need to execute 'check_consultation_slots' on TWVS Advisory & Consulting (twvs.co.za). Do NOT use this tool when another specialized tool fits better (use 'list_practice_areas' or 'get_partner_ecosystem' 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": "check_consultation_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
divisionNoAdvisory discipline required (financial_markets, restaurant_operations, or general).

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, and the description still adds genuinely new operational context: public unauthenticated access and a 60 requests/min per IP rate limit. It also repeats the read-only/idempotent claim, which is redundant but harmless, and the 'zero state mutation' phrasing is consistent 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.

Conciseness3/5

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

The scope statement is well front-loaded, but the 'When to use' sentence is pure filler that restates the tool name, and 'Returns' describes a generic envelope rather than real content. Roughly a third of the text does not earn its place.

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?

With one optional enum parameter, no output schema, and annotations covering the safety profile, the description supplies enough to call the tool correctly: scope, region coverage, auth/rate-limit behavior, and the shape of the response. Missing only concrete lead-time or channel detail, which is acceptable.

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?

Schema description coverage is 100% and the single 'division' parameter already documents its enum values, so the description's bare 'Parameters: division (optional)' adds nothing. Baseline 3 is appropriate when the schema carries full parameter meaning.

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 ('Retrieves current advisory consultation availability, lead times, and scheduling channels') and enumerates the covered regions, so the agent knows exactly what data comes back. It does not sharply delineate itself from 'submit_consultation_inquiry' beyond the generic exclusion sentence, keeping it short of a 5.

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 names three sibling tools to avoid, but the actual when-to-use clause is circular ('Call this tool when you specifically need to execute check_consultation_slots'), which conveys no condition. An agent learns the alternatives exist but not the situation that selects each one, so usage is only implied.

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