Skip to main content
Glama
LamantinAI

kaeru memory

by LamantinAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

cloud_initiatives

Read-only

Lists initiatives in a configured cloud so agents can review cloud-related goals and projects across sessions.

Instructions

List initiatives in one configured cloud.

Input Schema

NameRequiredDescriptionDefault
cloudNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / cloud / default
      Removed value: -null
    • removedInput schema / properties / cloud / description
      Removed value: -"Which cloud to ask. Required when several are configured."
    • addedInput schema / properties / cloud / minLength
      Added value: +1
    • changedInput schema / properties / cloud / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"CloudScopeParams"
  2. First observedv0.7.5

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint already establishes this as a safe read operation. The description adds the useful scoping constraint that only one configured cloud is queried, but it does not cover behavior such as missing cloud configuration, return shape, or pagination.

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?

The description is a single short sentence with the scope constraint front-loaded. It contains no redundant or filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list operation with annotations covering safety, the main missing piece is the meaning and expected values of the 'cloud' parameter. The description is minimally adequate but not complete for a caller unfamiliar with the configuration model.

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

Parameters2/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 explain the single 'cloud' parameter. It only says 'one configured cloud' and does not provide expected format, allowed values, or behavior when omitted, leaving the parameter meaning largely undocumented.

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 ('List') and resource ('initiatives') scoped to 'one configured cloud.' It is clearer than the bare name, though it does not explicitly contrast with siblings like initiatives or clouds.

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 phrase 'in one configured cloud' implies that the caller must already have a cloud configured and should pick one, but it gives no explicit when-to-use guidance or alternatives such as the sibling initiatives tool.

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