Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_payment_connections

Read-onlyIdempotent

Lists a company's payment provider connections, including provider-side accounts and statuses, so you can verify whether a provisioned NIF completed its connection.

Instructions

Returns the payment provider connections of a company your account owns or manages, with the provider-side account each one points at and its status. Use it to check whether a NIF you provisioned has completed its connection.

  • A NIF with no connections: answers 200 with an empty list.

  • environment: Test and Live connections are independent, so only the ones living in the mode of the key you ask with are returned; this field states which.

Closed catalogue. A NIF is not limited to one connection per provider: within a single environment it may hold several of the same provider, one per external account. What is unique is the external account itself — one live connection per provider, environment and external account. The set is still bounded and unpaginated: the collection carries no pagination and takes no page/limit, and every response holds the whole set for the environment of the key you ask with.

BeeL API endpoint: GET /v1/companies/{company_id}/payment-connections (reference: https://docs.beel.es)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "beel_list_payment_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesUnique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / company_id / description
      Previous value: -"NIF (company) the operation acts on. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A NIF you do not reach answers `403`, and so does a NIF that does not exist, so the existence of a NIF in another account is never disclosed."New value: +"Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed."
  2. First observedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds meaningful behavioral context beyond that: a missing NIF returns 200 with an empty list, Test and Live environments are independent, and the response is unpaginated with no page/limit parameters. It also explains that each external account may have multiple provider connections, which is useful for interpreting results.

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 first sentence front-loads the purpose and return content, and the bullet structure makes the environment and empty-list behavior easy to scan. The 'Closed catalogue' paragraph is somewhat dense and could be tighter, but it still earns its place by clarifying cardinality and pagination behavior.

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 one-parameter read-only list tool with no output schema, the description is complete enough: it covers the returned fields, empty-list behavior, environment scoping, pagination behavior, and the endpoint. The rich company_id schema description handles authorization and 403 semantics, so no critical context is missing.

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?

The single parameter has 100% schema description coverage, so the schema already explains that company_id is a UUID and that inaccessible or nonexistent companies return 403. The description reinforces the ownership scope ('company your account owns or manages') but does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Returns the payment provider connections of a company your account owns or manages, with the provider-side account each one points at and its status.' It also gives a concrete use case ('check whether a NIF you provisioned has completed its connection'), making the tool's purpose unmistakable and distinguishable from mutation siblings such as beel_update_payment_connection.

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 provides clear usage context by stating it is for checking whether a provisioned NIF has completed its connection. However, it does not explicitly name alternatives (e.g., beel_list_payment_events) or state when not to use this tool, so it falls short of the full when/when-not/alternatives guidance.

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