Skip to main content
Glama
Sign In

GetAccountED

by za.co.getaccounted
OverviewDiscussionsAdmin

VAT201 draft

accounting_vat201_draft
Read-onlyIdempotent

DRAFT VAT201 for a VAT period, field by field as on SARS eFiling (output tax, input tax, payable/refundable). A preparation draft — check it before filing on eFiling; nothing is submitted to SARS. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "accounting_vat201_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPeriod end YYYY-MM-DD
fromYesPeriod start YYYY-MM-DD
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it states that nothing is submitted to SARS, that the tool requires the user's GetAccountED sign-in, and that the user is prompted to sign in the first time. That auth/prerequisite disclosure is exactly the kind of behavioral context annotations cannot carry.

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?

Three tight sentences, front-loaded with the purpose and followed by the safety caveat and the auth requirement. 'Read-only' mildly duplicates readOnlyHint, but it reinforces the no-submission point rather than wasting space.

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

Completeness5/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 compensates by naming the fields the draft will contain (output tax, input tax, payable/refundable) plus the sign-in requirement and the non-filing guarantee. Nothing an agent needs in order to call this safely is missing.

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 coverage is 100% with per-parameter descriptions, including the business_id guidance pointing at accounting_list_my_businesses, so the schema already does the work. The description adds no additional meaning about the from/to period semantics beyond what the schema provides.

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?

Specific verb (DRAFT) and resource (VAT201 return for a VAT period), with an explicit statement of what it produces: output tax, input tax, payable/refundable, laid out field by field as on SARS eFiling. It is distinguishable from sa_vat_calculate by the 'preparation draft, nothing submitted' framing, though no sibling is named explicitly.

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?

Clear context for use: it is a preparation draft to check before filing on eFiling, and it does not submit anything to SARS. It does not, however, point the agent at alternatives (e.g. sa_vat_calculate for a plain VAT computation or accounting_emp201_detail for PAYE), so the when-not side is implied rather than stated.

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

All GetAccountED 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