Skip to main content
Glama

Kargom

Kargom account

get_account
Read-only

The connected Kargom account: name, balance (TRY), whether it can ship (sender profile complete), saved sender addresses (ids for quote_shipment) and this connection’s limits and usage today.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real substance beyond that by disclosing the returned fields and clarifying semantics ('whether it can ship' means the sender profile is complete) and that limits/usage are 'today'-scoped — useful because no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the resource and then lists the salient return fields, with no filler. The parenthetical asides are efficient, though the colon-and-list construction makes it slightly list-like rather than prose.

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?

With no output schema, the description must carry the burden of describing what comes back, and it does so at a useful level of detail (identity, balance, shippability, addresses, limits/usage). Nothing essential for calling a zero-parameter read tool appears to be missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The empty object schema with additionalProperties=false is consistent with the description's framing of a no-argument account read.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (the connected Kargom account) and enumerates exactly what it exposes: name, TRY balance, shippability, saved sender addresses, and connection limits/usage. It is clearly distinct from shipment-oriented siblings, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: the parenthetical '(ids for quote_shipment)' signals the intended downstream flow of pulling address ids before quoting a shipment. There is no explicit 'use this when...' guidance or exclusion of alternatives such as get_shipment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources