Skip to main content
Glama

Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres

Returns falling due, across your companies

portfolio_upcoming_filings
Read-only

What falls due between two dates in every company you may read the declarations of — the question a firm asks of all the books it keeps, and the one a person asks of the single company they run. "Portfolio" is meant as an accounting firm means it — its client portfolio — and is nothing but that: the companies you hold filings.read on, worked out at each call, never a list anybody maintains. Every one of them is in the answer, including a company whose country pack names no deadline, which is listed without a date and says so; a company left out would be indistinguishable from one that was never looked at. No country rule lives in this tool. It reads a calendar; it prepares and files nothing.

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": "portfolio_upcoming_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast day a return may fall due on.
fromYesFirst day a return may fall due on. Go back a few days to catch what is already late.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"First day a return may fall due on. Go back a few days to catch what is already late."
    • addedInput schema / properties / from / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / to / description
      Added value: +"Last day a return may fall due on."
    • addedInput schema / properties / to / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes well beyond that. It discloses that the company set is derived from filings.read permissions at each call and never from a maintained list, that companies with no named deadline in their country pack are still returned without a date, and that nothing is prepared or filed. These are non-obvious behavioral properties an agent could not infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core fact is front-loaded in the first clause, but the remainder is padded with figurative framing ('the question a firm asks of all the books it keeps') and a lengthy gloss on what 'portfolio' means. The genuinely informative sentences — inclusion of dateless companies, permission-derived scope, no country rules — are worth keeping; the rhetorical scaffolding is not.

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 read-only, two-parameter list tool with annotations and no output schema, the description covers what an agent needs: what is returned, that a company may appear with no date, and that scope is computed per call. It stops short of describing ordering or result volume, a modest gap given there is no output schema.

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% and both parameters are documented, including the hint to widen 'from' backwards for already-late returns. The description adds no format, boundary, or semantics beyond that, so the baseline of 3 applies.

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?

The opening clause names a specific resource and scope: what falls due between two dates across every company the caller can read filings for. It is identifiable against siblings like portfolio_filings_touched_since or contracts_deadlines, though the differentiation is implied by the date-window framing rather than stated outright. The metaphorical asides ('the question a firm asks of all the books it keeps') dilute rather than sharpen the purpose.

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

Usage Guidelines3/5

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

The description establishes boundaries usefully — 'No country rule lives in this tool. It reads a calendar; it prepares and files nothing' — which tells the agent this is not a filing or compliance-deadline tool. But it never names an alternative or an explicit condition for choosing this over portfolio_filings_touched_since, leaving usage to inference.

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.