Skip to main content
Glama

List catalog resource providers

list_catalog_resources
Read-onlyIdempotent

List the resource providers this server can provision from, such as a PostgreSQL database or an AI model: what each one is for, its plans and their limits, the first being the default, the environment variables an attachment sets, and a guide to using it from an app. Read it when choosing a resource and writing the app code that uses one. Requires connecting a Valet account.

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

Input Schema

NameRequiredDescriptionDefault
org_nameNoThe Valet organization to list for. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call resolved to; attach_resource lands in it. Empty when the server has no resource provider.
providersYesThe providers this server can provision a resource from. Empty when it has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / providers / items / properties / plans / items / properties / limits
      Added value: +{
      +  "description": "What the plan promises, such as its storage and connections, in display order. Absent for a plan with no limits, such as a model.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "display": {
      +        "description": "The limit's name for a person to read.",
      +        "type": "string"
      +      },
      +      "name": {
      +        "description": "The limit's name, such as storage or connections.",
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "The limit's value, such as 2 GiB or 20.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "display",
      +      "value"
      +    ],
      +    "type": "object"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • changedOutput schema / properties / providers / items / properties / plans / items / properties / name / description
      Previous value: -"The plan's name. Pass it as plan to attach_resource."New value: +"The plan's name. Pass it as plan to attach_resource or set_resource_plan."
  2. Changed10 schema fields changed
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call resolved to; attach_resource lands in it. Empty when the server has no resource provider."
    • addedOutput schema / properties / providers / description
      Added value: +"The providers this server can provision a resource from. Empty when it has none."
    • addedOutput schema / properties / providers / items / properties / description / description
      Added value: +"What the resource is and when an app needs one."
    • addedOutput schema / properties / providers / items / properties / display_name / description
      Added value: +"The provider's name for a person to read."
    • addedOutput schema / properties / providers / items / properties / env_vars / description
      Added value: +"Names of the environment variables an attachment sets, before any env_prefix."
    • addedOutput schema / properties / providers / items / properties / guide / description
      Added value: +"Markdown on how an app uses the resource once attached."
    • addedOutput schema / properties / providers / items / properties / name / description
      Added value: +"The provider's name. Pass it as provider to attach_resource."
    • addedOutput schema / properties / providers / items / properties / plans / description
      Added value: +"The provider's plans in its order. The first is what attach_resource provisions when no plan is named."
    • addedOutput schema / properties / providers / items / properties / plans / items / properties / display_name / description
      Added value: +"The plan's name for a person to read."
    • addedOutput schema / properties / providers / items / properties / plans / items / properties / name / description
      Added value: +"The plan's name. Pass it as plan to attach_resource."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "org": {
      +      "type": "string"
      +    },
      +    "providers": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "type": "string"
      +          },
      +          "display_name": {
      +            "type": "string"
      +          },
      +          "env_vars": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": [
      +              "null",
      +              "array"
      +            ]
      +          },
      +          "guide": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "plans": {
      +            "items": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "display_name": {
      +                  "type": "string"
      +                },
      +                "name": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "name",
      +                "display_name"
      +              ],
      +              "type": "object"
      +            },
      +            "type": [
      +              "null",
      +              "array"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "display_name",
      +          "description",
      +          "guide",
      +          "plans",
      +          "env_vars"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "providers"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered to the extent a catalog read can be. The description adds genuinely new behavioral context — the auth prerequisite ('Requires connecting a Valet account') and the shape of each entry including the default-first ordering of plans. It says nothing about result size, pagination, or whether the catalog varies by org, which matters since org_name changes scope.

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?

The purpose is front-loaded in the first clause, and the enumeration of returned fields is dense but each item is load-bearing for an agent deciding whether to call it. The middle sentence runs long and stacks five comma-separated items, which slightly hurts scannability but does not waste words.

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 an output schema present, the description is not obligated to explain return values, yet it usefully previews them; the auth prerequisite and the when-to-use trigger are both covered. What is missing is minor for a read-only, single-optional-param list tool — chiefly any hint about catalog size or org-scoped variance.

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% with a single optional parameter, so the schema already explains org_name and its default fallback. The description contributes no additional meaning about that parameter — nothing about how catalog contents differ across orgs. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and resource — 'List the resource providers this server can provision from' — and concretizes it with examples ('a PostgreSQL database or an AI model'). It enumerates exactly what each entry contains (purpose, plans and limits, default ordering, env vars set, usage guide), so an agent knows precisely what comes back. It stops short of explicitly contrasting with the sibling 'list_resources' (provisioned vs. available), so the boundary is inferable rather than stated.

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 a clear activation condition: 'Read it when choosing a resource and writing the app code that uses one,' which ties the tool to two concrete agent tasks. There is no explicit when-not guidance and no sibling is named as an alternative, which keeps it below a 5.

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