Cloche

List apps

list_apps

Read-only

Lists every app you can reach, with its URL and status. For when the person asks what they have, or when you need an app_id you are not already holding. Apps can share a name. The app_id tells them apart. Needs a sign-in, like every tool that touches an app. Without organization it lists your default organization, your personal one if you have it, and names any others. Organization lists one of those instead.

Input Schema

Name	Required	Description	Default
`organization`	No	the id of the organization to list. Omit for your default organization

Output Schema

Name	Required	Description
`apps`	Yes
`note`	No	plain sentences about this result for the person; the same text as the first text block
`shared`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / organization / description

Previous value: -"the id of the organization to list; omit to see your personal apps"New value: +"the id of the organization to list. Omit for your default organization"

Changed2 schema fields changedOct 29, 2026
- changedOutput schema / properties / apps / items / properties / kind / description
```
Previous value: -"\"app\" or \"skill\""New value: +"\"app\", \"skill\" or \"recipe\""
```
- changedOutput schema / properties / shared / items / properties / kind / description
```
Previous value: -"\"app\" or \"skill\""New value: +"\"app\", \"skill\" or \"recipe\""
```

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / organization / description

Previous value: -"which organization to list; omit to see your personal apps"New value: +"the id of the organization to list; omit to see your personal apps"

Changed2 schema fields changedOct 18, 2026
- addedOutput schema / properties / apps / items / properties / kind
```
Added value: +{
+  "description": "\"app\" or \"skill\"",
+  "type": "string"
+}
```
- addedOutput schema / properties / shared / items / properties / kind
```
Added value: +{
+  "description": "\"app\" or \"skill\"",
+  "type": "string"
+}
```
First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond that: a sign-in is required, and apps can share a name so app_id is the disambiguator. It does not address result size, pagination, or ordering for what is billed as an exhaustive list.

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?

Purpose and return fields are front-loaded, then usage, then caveats. It is tight overall, though the final two short sentences about organization read as clipped fragments and could be merged for smoother reading.

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

Completeness5/5

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

One optional parameter, an output schema that already defines the return shape, and annotations covering the safety profile — the description covers everything else an agent needs: auth requirement, default-scope behavior, and name-collision handling.

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 coverage is 100%, so the baseline is 3, but the description genuinely extends the organization parameter: omitting it lists the default organization, the personal one if present, and names any others, while supplying it lists that one instead. That scoping behavior is not in the schema text.

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 ("Lists every app you can reach") with the returned fields (URL and status). It also explains the app_id/duplicate-name relationship, which cleanly separates it from single-app siblings like get_app_context, get_app_status, or checkpoint_app.

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

Usage Guidelines4/5

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

Gives two concrete triggers: the person asks what they have, or you need an app_id you don't already hold — the latter implicitly says not to call it when you already have an id. It never names a sibling alternative (e.g. get_app_context) explicitly, so routing between app tools is only inferable.

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

All Cloche tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.