Skip to main content
Glama

Get Paybond Principal

paybond_get_principal
Read-only

Confirm the tenant-bound service-account identity behind your PAYBOND_API_KEY, returning tenant_id, subject, and roles. Use this prerequisite before tenant-scoped tools when tenant identity is unknown.

Instructions

Use this when you need to confirm which tenant-bound service-account principal the configured PAYBOND_API_KEY authenticates as (tenant_id, subject, and roles). Call early as a prerequisite before Harbor escrow, Signal reads, or other tenant-scoped tools when tenant identity is unknown. Not required before every later call once tenant_id is already known from a prior principal response or host config. Do not use this when you need Harbor intent escrow detail; use paybond_get_intent instead when you have an intent_id. Do not use this for A2A discovery; use paybond_get_a2a_agent_card instead. Makes one read-only external GET to the gateway principal endpoint; idempotent identity lookup with no side effects (no mutations, spend reservations, escrow changes, or ledger writes); auth or gateway failures surface as tool errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rolesNoRBAC roles granted to this principal for the authenticated tenant (example: ["operator"]).
subjectNoService-account subject identifier echoed by the gateway for the authenticated API key (example: service-account-1).
tenant_idNoTenant bound to the configured Paybond API key.
Behavior5/5

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

Annotations already set readOnlyHint=true; description adds concrete details: 'read-only external GET', 'idempotent identity lookup with no side effects', and clarifies error behavior. Fully consistent with annotations.

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?

Description is somewhat lengthy but each sentence adds value. It is front-loaded with purpose and structured with clear usage guidance. Could be slightly more concise but still effective.

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?

Given the tool has zero parameters and an output schema (present), the description fully covers purpose, usage context, behavioral traits, and comparisons to siblings. No gaps remain.

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?

No parameters exist, so schema coverage is 100% vacuously. The description does not need to add parameter info; baseline 4 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 uses specific verb 'confirm' and resource 'tenant-bound service-account principal', and clearly lists returned fields (tenant_id, subject, roles). It explicitly distinguishes from sibling tools by naming them.

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?

Provides explicit when to use (prerequisite before Harbor escrow, Signal reads when tenant identity unknown), when not to use (once tenant_id known, not for intent escrow or A2A discovery), and suggests alternatives (paybond_get_intent, paybond_get_a2a_agent_card).

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/nonameuserd/paybond-kit-python'

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