Skip to main content
Glama

list_available_services

Discover which credential-protected services you can access by listing available options stored in your password manager.

Instructions

List all services that the user has stored credentials for. Returns service names only, no secrets. Useful for discovering what credentials are available before making requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `toolListServices` function is the handler for `list_available_services`. It checks agent policy and retrieves services from the bridge.
    private async toolListServices(
      session: MCPSession,
      policies: AgentPolicy[],
    ): Promise<ToolCallResult> {
      const request: AccessRequest = {
        agentId: session.agentId,
        action: 'read',
      };
    
      const decision = this.policyEngine.evaluate(policies, request);
      await this.logAccess(session, 'list_services', undefined, decision);
    
      if (!decision.allowed) {
        return {
          content: [{ type: 'text', text: `Access denied: ${decision.reason}` }],
          isError: true,
        };
      }
    
      const services = await this.bridge.listServices(session.userId);
    
      return {
        content: [{ type: 'text', text: JSON.stringify({ services }) }],
      };
    }
  • The `list_available_services` tool definition, including name, description, and input schema.
        name: 'list_available_services',
        description:
          'List all services that the user has stored credentials for. Returns service names only, no secrets. Useful for discovering what credentials are available before making requests.',
        inputSchema: {
          type: 'object',
          properties: {},
        },
      },
    ];
Behavior3/5

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

No annotations provided, so description carries full burden. Adds valuable safety disclosure ('no secrets') and return format ('service names only'), but lacks other behavioral details like error handling when no credentials exist, caching behavior, or permission requirements.

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?

Three sentences with zero waste: purpose (List services...), behavioral constraint (Returns service names only...), and usage context (Useful for discovering...). Front-loaded and appropriately sized for tool complexity.

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?

Adequately compensates for missing output schema by stating return format. Complete for a zero-parameter discovery tool, though could mention behavior when no credentials are stored.

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?

Zero parameters present, meeting baseline of 4. Schema is empty object with 100% coverage (vacuously true), requiring no additional parameter documentation in description.

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?

States specific action (List) with clear resource scope (services with stored credentials) and distinguishes from siblings via 'service names only, no secrets'—contrasting with get_credential which presumably returns actual secrets and proxy_authenticated_request which consumes credentials.

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?

Provides clear contextual guidance ('Useful for discovering what credentials are available before making requests') establishing workflow position, though it could explicitly name siblings as alternatives/next steps rather than implying through 'before making requests'.

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/MARUCIE/authbox'

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