Meridian

List Apps

apps_list

Read-only

Lists the Meridian apps visible to the calling user, across all of their organisations by default. Returns each app's app_id, the identifier every other Meridian tool that targets a specific app (e.g. app_get) requires. Use whoami first to discover an organization_id if you want to narrow the search to one organisation.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of apps to return. Default 20, maximum 100.
`search`	No	Filters apps whose name contains this substring (case-insensitive).
`organization_id`	No	An organisation uuid or slug, as returned by `whoami`. When omitted, every organisation the user belongs to is searched.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: results are permission-scoped to the caller's visibility, span all organisations by default, and each result carries the `app_id` that downstream tools require. Pagination/limit behaviour is left to the schema.

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 short sentences, front-loaded with what the tool does and what it returns, followed by the prerequisite pointer. Every sentence carries information an agent needs; nothing is redundant.

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?

For a simple read-only list tool with no output schema, the description covers purpose, default scope, the key returned field and the prerequisite for filtering. It stops short of describing the overall result envelope (e.g. whether truncation at `limit` is signalled), which is the only remaining gap.

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%, so `limit`, `search` and `organization_id` are already fully documented, and the schema itself already points to `whoami` for the organization id. The description's only added meaning is reinforcing the default all-organisation scope, so 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 ("Lists the Meridian apps") plus the scope ("visible to the calling user, across all of their organisations by default"). It also implicitly distinguishes itself from the app-specific sibling by naming `app_get` as the tool that consumes the returned `app_id`.

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 an explicit routing instruction: call `whoami` first to obtain an `organization_id` when narrowing to one organisation, and states the default behaviour when it is omitted. It does not say when not to use this tool, but the context for use is clear.

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

All Meridian 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.

Resources

Need Help?