Skip to main content
Glama

Get Reputation Receipt

paybond_get_reputation_receipt
Read-only

Retrieve a signed Signal reputation receipt for a specific operator DID with score, metrics, reason codes, and Ed25519 signature. Returns null if no receipt exists for that operator and score version.

Instructions

Use this when you need the signed Signal reputation receipt for one known tenant-scoped operator DID (score, metrics, reason codes, and Ed25519 signing material under receipt). Requires PAYBOND_API_KEY with Signal analytics read access. Do not use this for tenant-wide aggregates—call paybond_get_portfolio_summary—or a portable signed operator list—call paybond_get_signed_portfolio_artifact—or one operator's fraud review posture—call paybond_get_fraud_assessment. Idempotent read with no side effects; returns null when no receipt exists for that operator and score_version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operator_didYesTenant-scoped operator DID whose signed Signal reputation receipt to fetch. Must belong to the authenticated tenant; do not invent tenant identifiers. Examples: did:web:vendor.example#booker-agent, did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK.
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
receiptNoSigned Signal receipt for the operator (tenant_id, operator_did, score_version, score, metrics, reason_codes, signing_algorithm, message_digest_hex, signing_public_key_hex, signature_hex).
updated_atNoRFC3339 timestamp when the stored receipt row was last updated.
schema_versionNoReputation receipt envelope schema version.
Behavior4/5

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

Describes idempotent read with no side effects and null return for missing receipts. Annotations already indicate readOnlyHint, but description adds idempotency and null behavior, enhancing transparency.

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 and well-structured. The main purpose is in the first sentence, followed by clear exclusions and behavioral details. No redundant information.

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 simple tool with 2 parameters, full schema coverage, and existing output schema, the description covers purpose, constraints, alternatives, and edge case (null return). Fully adequate.

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?

Schema coverage is 100%, so baseline is 3. The description adds context about the operator DID belonging to the authenticated tenant and provides examples, going beyond schema.

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?

Explicitly states the tool retrieves a signed Signal reputation receipt for a single tenant-scoped operator DID, with clear verb and resource. Distinguishes from three sibling tools by specifying what not to use it for.

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, when-not-to-use, and names alternative tools for other use cases (portfolio summary, signed portfolio artifact, fraud assessment). Also mentions required API key and read access.

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