Skip to main content
Glama

Lovie Company Formation

Get Calendar

filings_get_calendar
Read-only

Lists every filing the company owes, soonest first: the SEC Form D for a round, the state notices, the Delaware franchise tax and annual report, SEC filer access and its yearly confirmation, and yearly statements in other states. Each entry has its due date (computed, never estimated), why it is owed, its state, and anything only the founder can supply. A due date marked usual is not the authority's rule. Read-only.

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": {
      "companyId": "<companyId>"
    },
    "name": "filings_get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
asOfNo
entriesNo
edgarAccessNo
foreignQualificationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the closing 'Read-only.' adds nothing. The valuable additions are that due dates are computed rather than estimated, that 'usual' dates are not the authority's rule, and that entries flag items only the founder can supply — real behavioral context. The score would be higher if these caveats were tied more clearly to what the agent should do (e.g. which dates are reliable) rather than stated as asides.

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 sentences, front-loaded with scope and ordering, followed by per-entry content and a caveat about 'usual' dates. Dense and largely waste-free, but the trailing 'Read-only.' duplicates the annotations and could be dropped.

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?

An output schema exists, so return shape need not be explained, and the description still tells the agent what each entry contains (due date, why owed, state, founder-only inputs). For a single-parameter read tool this is close to complete; the missing piece is guidance on acting on the results versus the staging/filing tools.

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?

Only one parameter (companyId, a UUID wrapper) with 100% schema description coverage, so the schema carries the semantics. The description implies company scoping through 'the company owes' but adds nothing about the parameter's format, source, or behavior. Baseline 3 is appropriate.

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 description gives a specific verb and resource ('Lists every filing the company owes') plus ordering ('soonest first') and an explicit enumeration of the covered filing types (Form D, state notices, Delaware franchise tax, SEC filer access, other-state annual statements). That enumeration distinguishes it well from the staging siblings (filings_stage_form_d, filings_stage_franchise_tax) and from filings_compute_franchise_tax, though no sibling is named outright.

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?

Usage is implied only: the agent can infer this is the read-side compliance overview as opposed to the stage_* tools that prepare individual filings. There is no explicit when-to-use, no when-not, and no pointer to an alternative such as filings_get_prepared_filing for the detailed filing itself.

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.