Skip to main content
Glama
Sign In

stub

by africa.stub.api
OverviewDiscussionsAdmin

Create account

create_account

Create a new chart-of-accounts ledger account (an income, expense, asset, liability or equity account used to categorise transactions). Not a bank account — for that use create_bank_account.

Input Schema

NameRequiredDescriptionDefault
codeNoThe business's own account code (e.g. "4000"). Trimmed; blank means no code.
iconNoIcon identifier for the account (UI display).
metaNoOpaque metadata string stored on the account.
nameNoAccount name (e.g. "Consulting income", "Rent").
roleNoSemantic reporting role: "tax" (income-tax expense), "taxprovision" (tax provision/liability), or "salestax" (VAT control account). Omit for an ordinary account.
groupNoGroup label the account is organised under in the chart of accounts.
hiddenNoWhether the account is hidden from the chart-of-accounts UI.
deletedNoSoft-delete flag; true hides the account from active use.
journalNoJournal number classifying the account; maps to a standard journal name (e.g. sales, purchases, general).
premiumNoWhether the account is a premium-plan-only account.
primaryNoWhether this is the primary account of its kind.
parentidNoId of the parent account this nests under in the chart-of-accounts tree.
defaultidNoBuilt-in account id this custom account maps to: a number such as "410" or a string such as "za-coida" or "defaultvat".
baseaccountNoWhether this is a base/system account rather than a user-created one.
descriptionNoFree-text description of what the account is used for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / defaultid / description
      Previous value: -"Numeric id of the built-in/default account this custom account maps to."New value: +"Built-in account id this custom account maps to: a number such as \"410\" or a string such as \"za-coida\" or \"defaultvat\"."
  2. Changed1 schema field changed
    • addedInput schema / properties / code
      Added value: +{
+  "description": "The business's own account code (e.g. \"4000\"). Trimmed; blank means no code.",
+  "type": "string"
+}
  3. Changed14 schema fields changed
    • addedInput schema / properties / baseaccount / description
      Added value: +"Whether this is a base/system account rather than a user-created one."
    • addedInput schema / properties / defaultid / description
      Added value: +"Numeric id of the built-in/default account this custom account maps to."
    • addedInput schema / properties / deleted / description
      Added value: +"Soft-delete flag; true hides the account from active use."
    • addedInput schema / properties / description / description
      Added value: +"Free-text description of what the account is used for."
    • addedInput schema / properties / group / description
      Added value: +"Group label the account is organised under in the chart of accounts."
    • addedInput schema / properties / hidden / description
      Added value: +"Whether the account is hidden from the chart-of-accounts UI."
    • addedInput schema / properties / icon / description
      Added value: +"Icon identifier for the account (UI display)."
    • addedInput schema / properties / journal / description
      Added value: +"Journal number classifying the account; maps to a standard journal name (e.g. sales, purchases, general)."
    • addedInput schema / properties / meta / description
      Added value: +"Opaque metadata string stored on the account."
    • addedInput schema / properties / name / description
      Added value: +"Account name (e.g. \"Consulting income\", \"Rent\")."
    • addedInput schema / properties / parentid / description
      Added value: +"Id of the parent account this nests under in the chart-of-accounts tree."
    • addedInput schema / properties / premium / description
      Added value: +"Whether the account is a premium-plan-only account."
    • addedInput schema / properties / primary / description
      Added value: +"Whether this is the primary account of its kind."
    • addedInput schema / properties / role / description
      Added value: +"Semantic reporting role: \"tax\" (income-tax expense), \"taxprovision\" (tax provision/liability), or \"salestax\" (VAT control account). Omit for an ordinary account."
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description consistently describes a create operation. It adds useful domain context about chart-of-accounts accounts, but does not disclose validation behavior, duplicate handling, required logical fields, or authorization needs beyond what annotations and schema already 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?

Two compact sentences, front-loaded with the core action and immediately followed by the sibling disambiguation. Every clause carries useful selection or scoping information.

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 create tool with 15 optional parameters and no output schema, the description supplies enough domain and sibling context to select the tool correctly, while the schema carries the detailed field semantics. It could be stronger with a note about duplicate or empty-account behavior, but it is largely complete for 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 explains all 15 parameters thoroughly. The description adds no parameter-specific semantics beyond naming account categories generally, so the baseline of 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 gives a specific verb and resource: create a chart-of-accounts ledger account, and enumerates the account categories it covers. It also explicitly distinguishes this from create_bank_account, so an agent can select it without opening sibling schemas.

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?

It explicitly directs bank-account creation to create_bank_account, which is the most likely sibling confusion. However, it does not say when to create a new account versus update_account or list_accounts, nor does it mention prerequisites such as duplicate-code handling.

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

All stub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources