Skip to main content
Glama

List cluster partner institutions

list_cluster_partners
Read-onlyIdempotent

Cluster partner institutions grouped by catalogue category, with citation links.

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_cluster_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional: amrc | privileged | cooperation | global, or a category label

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / properties / category / maxLength
      Added value: +1000
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that results are grouped by catalogue category and include citation links, which is modest but real context about the response. It says nothing about ordering, empty results, or pagination.

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

Conciseness4/5

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

One short sentence fragment with zero filler and the grouping concept front-loaded. It is efficient, though being a fragment without a verb makes it slightly less immediately actionable than a full clause.

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?

This is a simple read-only list tool with one optional parameter and no output schema, so the description does not need to explain return values in depth. Still, an agent gets no guidance on when to call it versus the many other list_* siblings, which is the main remaining gap.

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 optional category parameter is fully documented with its allowed values in the schema. The description's phrase 'grouped by catalogue category' loosely echoes the parameter but adds no syntax or behavioral detail (e.g. what happens when omitted). 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 the resource (cluster partner institutions), its grouping (by catalogue category) and an extra output element (citation links), so an agent knows what it retrieves. It lacks an explicit verb and never contrasts itself with the sibling list_institutions, leaving differentiation to 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no mention of when to prefer list_institutions, and no note on whether the category filter is required or optional. Usage is only implied by the tool name.

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.