cledara-mcp

Upcoming renewals

upcoming_renewals

Read-onlyIdempotent

Identify applications renewing or due for payment within a specified number of days, listing soonest first with expected payment amounts and budget; inactive apps are excluded by default.

Instructions

Applications renewing or due a payment within the next N days, soonest first, with the expected payment amount and budget. Uses nextRenewalDate when Cledara sets it, otherwise the expected next payment date (see dateSource). Inactive and disabled apps are excluded unless includeInactive is true.

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

Input Schema

Name	Required	Description	Default
`withinDays`	No
`includeInactive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the bar is lower; the description still adds real behavioral detail — inactive/disabled apps are excluded by default, and the date used is nextRenewalDate when Cledara sets it, otherwise the expected next payment date as reflected in dateSource. It doesn't discuss result caps or ordering ties, but the date-source disclosure is the kind of context annotations can't provide.

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?

Three sentences, zero filler: what it returns and its order first, then the date-source rule, then the exclusion rule. Front-loaded and each sentence adds distinct information.

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 only two optional parameters, no output schema, and annotations covering the safety profile, the description supplies nearly everything needed: scope, ordering, date-source semantics, default exclusions. It stops short of noting whether the list is truncated or how empty results should be interpreted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it does for includeInactive by explaining the exact exclusion behavior it toggles. withinDays is only referenced as 'N days' with no note of the 0–366 bounds or default 30, leaving one parameter slightly under-explained.

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?

States a precise verb and resource — applications renewing or due payment within N days — plus ordering (soonest first) and return contents (expected payment amount and budget). It is clearly separable from list_applications or list_transactions in practice, though it never names a sibling to contrast with.

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 'within the next N days' framing implies the renewal-planning use case, and the includeInactive sentence clarifies a common filtering decision. But there is no explicit when-to-use versus missing_invoices or list_applications, and no guidance on choosing withinDays values or when results would be misleading.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server