Skip to main content
Glama

stub

by africa.stub.api
OverviewDiscussionsAdmin

Add entity salestax

add_entity_salestax

Add a sales tax to an entity. To add several taxes at once, prefer add_entity_salestaxes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo"salestax" | "levy" | "withholding"; blank means salestax.
nameNoDisplay name of the sales tax (e.g. "VAT").
rateNoSales tax rate as a DECIMAL FRACTION, e.g. 0.15 = 15% (NOT 15). A rate of 1.0 (100%) or higher is rejected.
orderNoStack position (default 0); components apply ascending.
amountNoExplicit sales tax amount; used instead of the rate when useamount is true.
entityYesEntity kind to add the sales tax to, e.g. "expense", "invoice".
compoundNoWhen true, this tax stacks on lower-order taxes' totals (default false).
entityidYesId of the entity to add the sales tax to.
parentidNoId of an existing salestax definition to link, instead of defining one inline.
exclusiveNoWhether the entity amount excludes this sales tax (tax added on top).
taxsourceNoStable locale rate-band identity, e.g. "locale:za/standard".
treatmentNo"standard" | "zeroRated" | "exempt"; blank/unknown means infer.
useamountNoWhen true, use amount as the tax figure instead of computing from the rate.
recoverableNoWhether this sales tax is recoverable (claimable as input tax).
referencenumberNoSales tax registration/reference number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior2/5

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

Annotations indicate a write operation (readOnlyHint=false, destructiveHint=false), but the description adds no behavioral context beyond the action itself. No mention of side effects, prerequisites, or how the addition affects existing tax calculations.

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 two short sentences, front-loading the primary purpose and then providing a concise usage alternative. No wasted words.

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 single-add tool with a rich schema and clear sibling distinction, the description is sufficient. It states the purpose and usage guidance; the schema covers parameters. A slightly more detailed behavioral note would be nice, but not essential.

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?

The input schema has 100% parameter description coverage, so the description does not need to explain parameters. The baseline of 3 applies; the description adds no extra meaning beyond 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?

Clearly states the action: 'Add a sales tax to an entity.' The verb 'add' and resource 'sales tax' are specific, and the mention of the plural sibling add_entity_salestaxes distinguishes it from the batch operation.

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

Usage Guidelines5/5

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

Explicitly guides when to use this tool vs. the alternative: 'To add several taxes at once, prefer add_entity_salestaxes.' This tells the agent to use this tool for a single tax addition, which is a clear usage direction.

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