Skip to main content
Glama
tradallo

tradallo-reputation

Official

get_utrs

Get paginated Universal Trade Receipts (UTRs) for any agent. Each UTR includes a Tradallo-recomputed SHA-256 hash for independent spot-checking. Filter by closing date and control page size.

Instructions

Fetch raw Universal Trade Receipts for an agent. Each UTR is a v2 canonical receipt with its SHA-256 hash recomputed by Tradallo so consumers can spot-check individual receipts. Paginated cursor-style on closed_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_handleYesThe agent's handle.
sinceNoISO timestamp; only return UTRs closed at or after this. Defaults to the agent's anchor.
limitNoPage size (default 100, max 500).

Implementation Reference

  • The MCP tool handler for 'get_utrs' — extracts agent_handle, constructs query string with optional 'since' and 'limit' params, calls client.getSigned() on /api/v1/agents/{handle}/utrs endpoint, and returns verified JSON data.
    case "get_utrs": {
      const handle = String((args as { agent_handle?: unknown })?.agent_handle ?? "").trim();
      if (!handle) return errorResult("agent_handle is required");
      const qs = new URLSearchParams();
      const sinceArg = (args as { since?: unknown })?.since;
      const limitArg = (args as { limit?: unknown })?.limit;
      if (typeof sinceArg === "string") qs.set("since", sinceArg);
      if (typeof limitArg === "number") qs.set("limit", String(limitArg));
      const path = `/api/v1/agents/${encodeURIComponent(handle)}/utrs${qs.toString() ? `?${qs.toString()}` : ""}`;
      const data = await client.getSigned<unknown>(path);
      return jsonResult(data);
    }
  • Input schema and description for the 'get_utrs' tool registration — defines agent_handle (required), since (optional ISO date-time), and limit (optional integer 1-500) parameters.
    {
      name: "get_utrs",
      description:
        "Fetch raw Universal Trade Receipts for an agent. Each UTR is a v2 canonical receipt with its SHA-256 hash recomputed by Tradallo so consumers can spot-check individual receipts against `verify_utr`. Paginated cursor-style on closed_at — pass the prior response's `next_since` to advance.\n\nExample:\n  - get_utrs(\"alpha-momentum-v3\", undefined, 50)",
      inputSchema: {
        type: "object",
        properties: {
          agent_handle: { type: "string", minLength: 1, maxLength: 40, pattern: "^[a-z0-9_-]+$", description: "The agent's handle." },
          since: {
            type: "string",
            format: "date-time",
            description: "ISO timestamp; only return UTRs closed at or after this. Defaults to the agent's registration anchor.",
          },
          limit: { type: "integer", minimum: 1, maximum: 500, default: 100, description: "Page size (1-500)." },
        },
        required: ["agent_handle"],
      },
      annotations: READ_ONLY_ANNOTATIONS,
    },
  • src/index.ts:157-175 (registration)
    Tool named 'get_utrs' registered in the MCP ListToolsRequestSchema handler as part of the tool catalog (line 76-176).
    {
      name: "get_utrs",
      description:
        "Fetch raw Universal Trade Receipts for an agent. Each UTR is a v2 canonical receipt with its SHA-256 hash recomputed by Tradallo so consumers can spot-check individual receipts against `verify_utr`. Paginated cursor-style on closed_at — pass the prior response's `next_since` to advance.\n\nExample:\n  - get_utrs(\"alpha-momentum-v3\", undefined, 50)",
      inputSchema: {
        type: "object",
        properties: {
          agent_handle: { type: "string", minLength: 1, maxLength: 40, pattern: "^[a-z0-9_-]+$", description: "The agent's handle." },
          since: {
            type: "string",
            format: "date-time",
            description: "ISO timestamp; only return UTRs closed at or after this. Defaults to the agent's registration anchor.",
          },
          limit: { type: "integer", minimum: 1, maximum: 500, default: 100, description: "Page size (1-500)." },
        },
        required: ["agent_handle"],
      },
      annotations: READ_ONLY_ANNOTATIONS,
    },
  • The client.getSigned() helper used by the handler to fetch and cryptographically verify the signed envelope from the Tradallo API.
    async getSigned<T>(path: string): Promise<T> {
      const res = await fetch(`${this.baseUrl}${path}`, {
        headers: { ...this.headers, accept: "application/json" },
      });
      if (res.status === 404) {
        throw new Error(`not_found: ${path}`);
      }
      if (!res.ok) {
        throw new Error(`request failed: ${res.status} ${res.statusText} (${path})`);
      }
      const envelope = (await res.json()) as SignedEnvelope<T>;
      await this.verifyEnvelope(envelope);
      return envelope.data;
    }
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that each UTR's SHA-256 hash is recomputed for spot-checking, and pagination is cursor-style on closed_at. This reveals behavioral traits beyond a simple fetch, though auth requirements and side effects are not mentioned.

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?

The description is three sentences, front-loaded with purpose, followed by relevant detail and pagination. No redundant information, every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not fully explain return format or pagination details like cursor handling. It mentions 'v2 canonical receipt' and hash, but an agent might need more clarity on response structure. Adequate but with gaps.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema, only implicitly relating closed_at to the 'since' parameter via pagination mention. No further parameter details are provided.

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 clearly states the tool fetches raw Universal Trade Receipts for an agent, specifies the resource and action, and distinguishes from siblings by mentioning it provides v2 canonical receipts with recomputed SHA-256 hashes. It also notes pagination, setting it apart from other tools like verify_utr.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by describing the tool's function but lacks explicit guidance on when to use this tool versus its siblings (e.g., get_track_record, verify_utr). No when-not-to-use or alternative suggestions are provided.

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/tradallo/reputation'

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