Skip to main content
Glama

The Valley Desk

List institutions

list_institutions
Read-onlyIdempotent

List the regional institutions in The Valley Desk directory with the number of listings recorded for each. Use a returned name as the institution filter in search.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
truncatedNo
institutionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safe, local, read-only profile is covered. The description adds useful behavior beyond that: the payload includes a per-institution listing count and the names double as filter values. It says nothing about ordering, pagination, or whether institutions with zero listings are included, which limits the added value.

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?

Two short sentences, with the core purpose and the returned data up front and the follow-up workflow second. Nothing is redundant, and no sentence is wasted.

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

Completeness5/5

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

For a zero-argument listing tool with a full annotation set and an output schema, this is enough. The description covers purpose, the returned count, and the follow-up use of the names, so an agent can invoke it correctly without more detail.

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?

The tool takes zero parameters, so there is no parameter meaning to document; that baseline is a 4. The description correctly implies there are no filtering inputs by describing an unfiltered directory listing.

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?

A specific verb plus resource: 'List the regional institutions in The Valley Desk directory', with the additional scope of returning counts per institution. That clearly separates it from list_topics_and_counties and search, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives concrete downstream guidance: 'Use a returned name as the institution filter in search', which tells an agent both when to call this first and how to chain it. There is no explicit exclusion clause, but the workflow context is clear.

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.