Skip to main content
Glama

TWVS — Industrial Valves & Engineering Supply Catalog

Get Partner Ecosystem

get_partner_ecosystem
Read-onlyIdempotent

Details enterprise technology solution partnerships including Tegra Solutions (Axway, Cato Networks, Salt Security), Omnea Financial Middleware, SmartStream, and Integrated Hosting Solutions. When to use: Call this tool when you specifically need to execute 'get_partner_ecosystem' on TWVS Advisory & Consulting (twvs.co.za). Do NOT use this tool when another specialized tool fits better (use 'list_practice_areas' or 'check_consultation_slots' or 'submit_consultation_inquiry' for their respective operations). Parameters: partner_name (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": "get_partner_ecosystem"
  }
}

Input Schema

NameRequiredDescriptionDefault
partner_nameNoOptional filter for a specific partner (e.g. axway, cato, salt, omnea, smartstream, tegra, integrated hosting).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety profile is covered. The description adds value beyond them by disclosing the 60 requests/min per IP rate limit, unauthenticated public access, and the shape of the response (status, matched records or computed metrics, canonical action URLs). Minor redundancy in restating 'strictly read-only, idempotent, zero state mutation' keeps it from 5.

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 content is organized into clearly labelled sections — purpose, when to use, exclusions, parameters, behavior, returns — and the substantive partner list is front-loaded. The circular usage sentence is wasteful, but the overall structure is easy to scan and nothing essential is buried.

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 no output schema, the description carries the burden of explaining returns, and it does so at a useful level (status, matched records or metrics, canonical action URLs). For a single-optional-parameter read tool this is close to sufficient; only the matching/filtering semantics of partner_name are left unstated.

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 partner_name parameter already carries its own description with worked examples (axway, cato, salt, omnea, smartstream, tegra, integrated hosting). The description only repeats that the parameter is optional and adds no matching semantics such as substring vs exact matching or case sensitivity, so the 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 description names a specific resource (enterprise technology solution partnerships) and enumerates its contents — Tegra Solutions vendors, Omnea Financial Middleware, SmartStream, Integrated Hosting. An agent can tell this is a lookup of partner ecosystem data. It stops short of 5 because it doesn't contrast meaningfully with any sibling that could plausibly be confused with it.

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?

There is a 'When to use' sentence, but it is circular — 'call this tool when you specifically need to execute get_partner_ecosystem' adds no decision criteria. The 'Do NOT use' clause names list_practice_areas, check_consultation_slots, and submit_consultation_inquiry, which are obviously unrelated operations rather than genuine alternatives for partner data, so the exclusion doesn't sharpen selection.

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