Skip to main content
Glama

providers

List configured payment providers and their capabilities to manage transaction routing and processing within the Junto MCP server.

Instructions

List configured payment providers and their capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool "providers" is defined and implemented in src/index.ts. It iterates over the configured providers map and returns their information via jsonResult.
    // Tool: providers
    server.tool(
      "providers",
      "List configured payment providers and their capabilities.",
      {},
      async () => {
        const list = Array.from(providers.values()).map((p) => p.info());
        return jsonResult(list);
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. Adds value by mentioning 'capabilities' (what providers can do), but lacks operational details like read-only safety, caching behavior, or response format that annotations would typically cover.

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?

Single sentence with zero waste. Front-loaded with verb and resource. Appropriate length for a simple discovery tool with no parameters.

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?

Adequate for a low-complexity tool (0 params, no nested objects). Specifies return value content (providers + capabilities) even without output schema. Could improve by mentioning return format or structure.

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?

Input schema has zero parameters. Per baseline rules for 0-param tools, score is 4.

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?

Uses specific verb 'List' with clear resource 'configured payment providers' and includes 'capabilities' to specify scope. Distinct from action-oriented siblings (charge, pay, refund) and status tools (balance, status, limits).

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?

No explicit when-to-use or alternative guidance provided. However, usage is implied by the contrast with transactional siblings - this is a discovery/configuration tool versus payment execution tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vrllrv/junto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server