Skip to main content
Glama

TWVS — Industrial Valves & Engineering Supply Catalog

Get Company Profile

get_company_profile
Read-onlyIdempotent

Returns TWVS executive leadership credentials, founding partners, headquarters location, and verified corporate contact channels. When to use: Call this tool when you specifically need to execute 'get_company_profile' 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 'check_consultation_slots' for their respective operations). Parameters: none required (zero-argument query). 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": "get_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is redundant here. The description does add genuinely new context beyond annotations: public unauthenticated access and a rate limit of 60 requests/min per IP. That is useful, but the rest of the section ('zero state mutation') merely repeats structured data.

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?

Front-loaded and sectioned (when to use, parameters, behavior, returns), which helps scanning. But sentences such as 'Call this tool when you specifically need to execute get_company_profile on TWVS Advisory & Consulting (twvs.co.za)' are padding, and the returns boilerplate ('computed metrics') does not fit a static profile lookup.

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?

With no output schema, the description is responsible for return shape; it names status, matched records and action URLs, but reuses a generic template ('computed metrics', 'matched records') that does not match a single-company profile fetch, and it never says what fields come back. Adequate for a zero-argument read, but the return section is boilerplate rather than accurate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, which sets the baseline at 4; the description's 'Parameters: none required (zero-argument query)' is consistent with the empty schema and leaves no ambiguity. It is redundant with the schema but not misleading.

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?

States a specific verb and resource plus the actual content of the payload: executive leadership credentials, founding partners, headquarters location, and verified contact channels for TWVS Advisory & Consulting. This is far more specific than the title and lets an agent distinguish it from siblings without opening any schema.

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 list the alternatives it is not (list_practice_areas, get_partner_ecosystem, check_consultation_slots), which is real routing value. However, the positive condition is circular - "call this tool when you specifically need to execute 'get_company_profile'" restates the name rather than describing a user intent or scenario, so the agent gets no actual trigger condition.

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