Skip to main content
Glama
Sign In
cledara-mcp

cledara-mcp

by ilyesBen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Cledara applications

list_applications
Read-onlyIdempotent

List SaaS applications in a Cledara workspace with status, owner, teams, budget, balance, next renewal date, and expected next payment; optionally filter by team, owner, name, or status.

Instructions

List SaaS applications in the Cledara workspace with status, owner, teams, budget, balance, next renewal date and expected next payment. Filters are optional.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam name (substring) or team ID.
ownerNoOwner name (substring) or owner ID.
searchNoCase-insensitive substring match on the application name.
statusNoOnly these statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description's added value is the enumeration of returned fields, but it says nothing about pagination, result caps, or ordering -- meaningful gaps for a list tool on an open-world API.

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?

Two tight sentences: the capability and returned fields come first, the optional-filter note last. No filler, nothing buried.

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 correctly compensates by listing the fields returned, which is the key context an agent needs to plan downstream use. Missing only pagination/volume expectations for an open-world list endpoint.

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%, with each of the four filters documented including matching semantics (substring, case-insensitive) and the status enum. The description adds only that filters are optional, which is already implied by zero required parameters, so it provides no meaning beyond the schema.

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 specific verb and resource ('List SaaS applications in the Cledara workspace') and enumerates the returned fields, so an agent knows exactly what it gets. It doesn't name a sibling to distinguish itself from, e.g., upcoming_renewals, even though both touch renewal data, so it stops short of a 5.

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?

'Filters are optional' implicitly tells the agent it can call with no arguments to retrieve everything -- a useful usage cue. However, it never says when to prefer this over sibling tools like upcoming_renewals or spend_summary, nor any exclusions, so guidance is only implied.

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

Deploy Server

Other Tools