Skip to main content
Glama
theagoralabs

Theagora MCP Server

by theagoralabs

my_purchases

Read-only

View your transaction history as a buyer, showing all escrows created, their states, and settlement outcomes.

Instructions

View your transaction history as a buyer. Shows all escrows you have created, their states, and settlement outcomes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The my_purchases tool registration and handler function. It calls client.getTransactions() to retrieve the buyer's transaction history and returns the results as formatted JSON.
    // my_purchases — View transaction history
    server.tool(
      'my_purchases',
      'View your transaction history as a buyer. Shows all escrows you have created, their states, and settlement outcomes.',
      {},
      { readOnlyHint: true, openWorldHint: true },
      async () => {
        const result = await client.getTransactions();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Input schema for my_purchases tool - empty object indicating no parameters are required.
    {},
  • src/index.ts:23-23 (registration)
    Registration point where registerBuyingTools is called to register the my_purchases tool along with other buying-related tools.
    registerBuyingTools(server, client);
  • The AgoraApiClient.getTransactions() method implementation that makes the actual HTTP request to /transactions endpoint.
    async getTransactions(): Promise<any> {
      return this.request('/transactions');
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe, read-only operation with potentially large data. The description adds context by specifying what data is shown (escrows, states, settlement outcomes), which is useful but does not detail behavioral traits like pagination, rate limits, or data freshness beyond what annotations provide.

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 front-loaded with the core purpose in the first sentence and adds specific details in the second, with no wasted words. Every sentence earns its place by clarifying scope and content efficiently.

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

Completeness4/5

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

Given the tool's complexity (simple read-only with no parameters) and annotations covering safety and scope, the description is mostly complete by specifying what data is returned. However, without an output schema, it could benefit from more detail on return format (e.g., list structure, fields), though it's adequate for the context.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description does not need to add parameter details, so it appropriately focuses on output semantics, earning a baseline score of 4 for not over-explaining what's already clear in the 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?

The description clearly states the tool's purpose with a specific verb ('View') and resource ('your transaction history as a buyer'), and distinguishes it from siblings by specifying it shows escrows created by the user, not other transaction types like sales or orders. This makes it easy to differentiate from tools like 'my_sales' or 'my_orders'.

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?

The description implies usage context by specifying 'as a buyer' and focusing on escrows created by the user, which helps distinguish it from tools like 'my_sales' or 'check_escrow'. However, it does not explicitly state when not to use it or name alternatives, such as for viewing sales or specific escrow checks.

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/theagoralabs/mcp'

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