Skip to main content
Glama

Get Signed Portfolio Artifact

paybond_get_signed_portfolio_artifact
Read-only

Retrieve a signed, tenant-scoped Signal portfolio snapshot with operator list and Ed25519 signing material for offline verification or partner sharing.

Instructions

Use this when you need a portable, tenant-scoped signed Signal portfolio snapshot (operator list plus Ed25519 signing material) for offline verifier checks or partner sharing—not a public leaderboard. Requires PAYBOND_API_KEY with Signal analytics read access. Omit score_version to use the gateway default current model (1.0). Do not use this for tenant-wide aggregates without signatures—call paybond_get_portfolio_summary—or for one operator's signed receipt—call paybond_get_reputation_receipt—or for one operator's fraud review posture—call paybond_get_fraud_assessment. Idempotent read with no side effects; auth, RBAC, feature, or gateway failures surface as tool errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
score_versionNoOptional Signal score model version to query. Omit to use the gateway default current model (1.0). Example: 1.0.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoArtifact kind identifier (currently paybond.signal.portfolio_snapshot).
tenant_idNoTenant echoed by the gateway for the authenticated API key (example: tenant-a). Never invent tenant identifiers.
signature_hexNoEd25519 signature hex over the canonical portfolio artifact payload.
score_model_versionNoScore model version used for the artifact (echoes the requested score_version or the gateway default 1.0).
checkpoint_last_ledger_seqNoLast ledger sequence included in the tenant Signal checkpoint for this artifact.
Behavior5/5

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

Describes idempotent read with no side effects and error handling (auth/RBAC/gateway failures surface as errors), adding context beyond readOnlyHint annotation.

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?

Concise single paragraph front-loading purpose, followed by usage guidelines and behavioral details; every sentence contributes meaningfully.

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?

Covers purpose, usage, behavioral transparency, parameter default, and tenant scope; output schema exists so return info not needed; fully adequate for agent invocation.

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?

Single optional parameter with schema coverage 100%; description adds value by explaining omission defaults to current model (1.0), though mostly aligns with schema 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?

Clearly states the tool retrieves a signed portfolio artifact for offline/partner sharing, distinguishes from public leaderboard and sibling tools like paybond_get_portfolio_summary and paybond_get_reputation_receipt.

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?

Explicitly states when to use (portable signed snapshot) and when not to (for aggregates, receipts, fraud assessment), and names alternative tools for each case.

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