Skip to main content
Glama
auraajenticai

Aura Courier MCP

by auraajenticai
OverviewSchemaSourceRelated ServersDiscussionsAdmin

get_balance

Check your merchant account balance and payout details for a selected courier provider to track available funds.

Instructions

Retrieve current merchant account balance and payout details from a courier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
courierYesCourier provider to check balance for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / courier / default
      Removed value: -"steadfast"
    • addedInput schema / properties / courier / description
      Added value: +"Courier provider to check balance for"
    • changedInput schema / properties / courier / enum
      Previous value: -[
-  "steadfast",
-  "pathao",
-  "redx",
-  "paperfly"
-]New value: +[
+  "steadfast",
+  "pathao"
+]
    • addedInput schema / required
      Added value: +[
+  "courier"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. 'Retrieve' and 'current' imply a safe, read-only, fresh data lookup, which is helpful. However, it does not disclose potential errors, authentication requirements, or the shape/scope of 'payout details,' leaving some behavioral ambiguity.

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?

One tight sentence with no filler. The core action and object are front-loaded, and the courier scoping is immediately clear.

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?

For a one-parameter tool with no output schema, the description covers what the agent needs to decide to call it and what it will get back at a high level (balance and payout details). It is slightly incomplete in not detailing payout details or return format, but not enough to block correct invocation.

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 the schema already fully documents the single 'courier' parameter, including its enum values. The main description adds no extra parameter meaning beyond reinforcing that the balance is checked 'from a courier,' which matches the schema. Baseline 3 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 opens with a specific verb ('Retrieve') and a precise resource ('current merchant account balance and payout details') scoped to a courier provider. Among the sibling tools, none covers balance/payout retrieval, so the tool is clearly distinguishable without opening the schema.

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 gives clear context: use this tool when you need a merchant account balance or payout details for a specific courier. It does not explicitly name alternatives or exclusions, but the sibling tools are distinct operations (tracking, parcel creation, rate comparison), so confusion is unlikely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools