Skip to main content
Glama

Get Gifi Status

get_gifi_status
Read-onlyIdempotent

Canada: is my GIFI ready for the T2, which accounts are not mapped or need review, and do the balance checks pass. 'is my GIFI ready', 'GIFI mapping', 'T2 schedule 100 / 125'. Maps any new accounts first. AccountsOS prepares the GIFI trial balance for the accountant's T2 software, it does not prepare or file the T2.

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_gifi_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_atNoYear to date instead of a full year: schedule 100 at this date (YYYY-MM-DD), schedule 125 from the fiscal year start to it. Use for "GIFI at 28 Oct" or the current year so far.
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.
year_endNoThe fiscal year end, YYYY-MM-DD. Omit for the last completed fiscal year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_at
      Added value: +{
      +  "description": "Year to date instead of a full year: schedule 100 at this date (YYYY-MM-DD), schedule 125 from the fiscal year start to it. Use for \"GIFI at 28 Oct\" or the current year so far.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior2/5

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

The description discloses a side effect — 'Maps any new accounts first' — which is genuinely useful behavioral context the annotations do not carry, but auto-mapping GIFI accounts is a persistent state change that sits awkwardly against readOnlyHint=true and idempotentHint=true. Aside from that it adds no information about rate limits, permissions, or what happens to previously mapped accounts; the safety profile is left entirely to the annotations.

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?

The core question leads, followed by trigger phrases and the scope boundary — good front-loading with no filler sentences. It reads as a string of fragments rather than prose, and the mapping side effect is buried mid-paragraph where it deserves more prominence given its behavioral implications.

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 three-optional-parameter, read-only status tool with no output schema and full schema coverage, the description covers purpose, triggers, and the filing boundary. The main gap is that the auto-mapping behavior and its consequences (does it alter stored mappings the accountant reviews?) are left underexplained.

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%, so as_at, company, and year_end are already fully documented, including the schedule 100 vs 125 split for a partial year. The description adds no parameter-level meaning beyond that, which meets the baseline-3 expectation when the schema does the work.

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 states a specific resource and jurisdiction (Canadian GIFI trial balance for the T2) and enumerates exactly what it answers: readiness, unmapped/review accounts, and balance-check results. The domain qualifiers (GIFI, schedule 100/125) make it clearly distinguishable from generic siblings like get_accounts_status or get_reconciliation_status without reading either 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?

It supplies concrete invocation triggers ('is my GIFI ready', 'GIFI mapping', 'T2 schedule 100 / 125') and draws an explicit boundary that it does not prepare or file the T2. What is missing is routing to an alternative — it never names the tool to use for the actual T2 preparation or filing when that is what the user wants.

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.