Skip to main content
Glama
vishalsg42

munim

by vishalsg42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_provider_tools

Lists tools published by a connected provider account, returning names, schemas, and read-only flags. Filter by name, description, or argument schema to find specific tools like those accepting teamId.

Instructions

List the tools this client's account with this provider actually publishes.

Returns each tool's name, description, argument schema, and whether the provider marks it read-only. read_only is what the provider says about its own tool; null means it said nothing, and it is reported rather than enforced.

Read this before call_provider_tool, which invokes one of them. Start with names_only, which returns names and read-only flags alone: for Resend that is 2KB against 122KB, and the full listing has exceeded a caller's response limit outright. matching filters on the name, the description and the argument schema, so "which tools take a teamId" is answerable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientYesThe client to act on, by the name you registered them under. A write resolves this one client's credentials and no other.
matchingNoOnly tools whose name, description or argument schema contains this. Searching the schema is how you find every tool that takes a teamId.
providerYesThe provider to use, for example cloudflare, vercel or resend. Only what this client is actually connected to is reachable.
names_onlyNoReturn names and read-only flags only. Resend publishes 121KB of schemas and 2KB of names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / client / description
      Added value: +"The client to act on, by the name you registered them under. A write resolves this one client's credentials and no other."
    • addedInput schema / properties / matching / description
      Added value: +"Only tools whose name, description or argument schema contains this. Searching the schema is how you find every tool that takes a teamId."
    • addedInput schema / properties / names_only / description
      Added value: +"Return names and read-only flags only. Resend publishes 121KB of schemas and 2KB of names."
    • addedInput schema / properties / provider / description
      Added value: +"The provider to use, for example cloudflare, vercel or resend. Only what this client is actually connected to is reachable."
  2. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the return fields, explains that `read_only` is reported not enforced, and warns about response size limits, recommending `names_only` as a workaround. It does not cover authentication or error conditions, but for a listing tool that is acceptable.

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 description is organized into clear sections: purpose, return details, and usage guidance. Every sentence contributes useful information—no filler. It is slightly long but efficiently structured with line breaks for readability.

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?

Given 4 parameters and no output schema, the description explains what is returned, how to filter, and how to avoid response limits. It covers the key behaviors an agent needs to call correctly, though it does not detail error handling or authentication. Overall, it is sufficiently complete for the tool's complexity.

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?

While the schema already describes each parameter, the description adds valuable context: `names_only` is optimized to reduce payload (2KB vs 122KB for Resend) and `matching` searches across name, description, and schema to answer questions like 'which tools take a teamId'. This enriches the parameter meaning beyond the schema.

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?

The description clearly states the tool lists the tools a client's account with a provider publishes. It explicitly distinguishes from sibling `call_provider_tool` by saying to read this before invoking that one, and contrasts with other siblings like `call_provider_api` by focusing on tool listing.

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

Usage Guidelines5/5

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

The description provides explicit guidance: read this before `call_provider_tool`, use `names_only` for lightweight calls, and use `matching` for filtering. It clearly identifies when to use this tool versus alternatives and even gives size-based rationale.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools