Skip to main content
Glama

taxapp.nz

Send a scheduled report now

send_scheduled_report_now

Emails a scheduled report now, by its id from list_scheduled_reports, to its recipient and everyone copied, covering the period its next run will cover. Its schedule stays as it is. It sends an email every time, so confirm with the person first. Only for an organisation where this connection may add and change records (list_organisations says which). The answer says who it was sent to.

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": {
      "scheduled_report_id": "<scheduled_report_id>"
    },
    "name": "send_scheduled_report_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
organisation_idNoThe id of the organisation to use, from list_organisations. Leave it out when the connection covers only one organisation; it is required when it covers more than one.
scheduled_report_idYesThe schedule's id, from list_scheduled_reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world. The description adds real value on top: an email is sent every single time (reinforcing non-idempotency with an operational warning to confirm first), the schedule itself is not modified, and the period covered is the next scheduled run's period. Return content is also noted.

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?

Front-loads the action and keeps to a small number of dense, purposeful sentences; each sentence carries distinct information (source of id, recipient set, coverage period, immutability, non-idempotent warning, permission gate, return values). Slightly run-on but not wasteful.

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?

No output schema exists, and the description compensates by stating the answer reports who it was sent to. Permission gating, side-effect warning, and immutability are all covered. Only the exact return payload shape is left vague, which is acceptable for a send action.

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% and both parameters are documented there, including the conditional requirement on organisation_id. The description only reiterates that the id comes from list_scheduled_reports, adding nothing the schema does not already say, so baseline 3 applies.

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?

States a specific verb and resource ('Emails a scheduled report now') and scopes it precisely: send the report tied to a schedule id, to its recipient and cc'd parties, without altering the schedule. This is clearly distinguishable from create_scheduled_report, update_scheduled_report, and list_scheduled_reports.

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?

Gives strong contextual routing: fetch the id from list_scheduled_reports, and only use it for an organisation where the connection may add and change records (check list_organisations). It also advises confirming with the person first. It stops short of explicitly contrasting with alternatives like update_scheduled_report, so it is not a full 5.

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.