Skip to main content
Glama

Get Compliance Calendar

get_compliance_calendar
Read-only

Returns the compliance and filing deadlines that generally apply to a company of this state and entity type. These are dates to be aware of, not bills or confirmed obligations: never tell the user they owe a payment or will be penalised because of an entry. When formationCompleted is false the company is not formed yet, so the dates are informational. For the user's own task list, call get_compliance_checklist instead.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), and the description adds real behavioral context beyond them: the data is informational rather than obligations, and when formationCompleted is false the company is unformed so the dates are provisional. It does not describe the shape or volume of returned dates, which keeps it short of a 5.

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

Conciseness5/5

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

Four tightly packed sentences, purpose front-loaded, each carrying distinct information: purpose, interpretive guardrail, the unformed-company edge case, and the sibling handoff. No filler or repetition.

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?

With no output schema, the description could say more about what a returned entry looks like (deadline types, dates, applicability), and it references formationCompleted without noting it derives from server-side company state rather than an input. Still, the agent has enough to call it correctly and to interpret results safely.

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 all three parameters are optional analytics fields, so the schema already fully documents them. The description adds no parameter guidance, but none is needed for analytics-only inputs; 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 ("Returns the compliance and filing deadlines") plus the applicability scope ("a company of this state and entity type"), and explicitly names the sibling it is not for (get_compliance_checklist). An agent can distinguish it from the checklist tool without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use (company deadlines for this state/entity type), an explicit when-not/alternative ("For the user's own task list, call get_compliance_checklist instead"), and an interpretation rule ("never tell the user they owe a payment or will be penalised"). Nothing about selection is left 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.