Skip to main content
Glama
Sign In
whodb-cli

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_apps

Read-onlyIdempotent

List hosted ontology-powered apps in a project, with optional workspace, name, type, status, deployment, and pagination filters for targeted app discovery.

Instructions

List hosted ontology-powered apps in the selected project. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional case-insensitive name substring filter for list tools
typeNoOptional type filter, for example provider type, transform trigger mode, or function language
limitNoMaximum list items to return; use offset to continue
fieldsNoTop-level output fields to include. Prefer only fields needed now; call again with more fields if needed.
offsetNoNumber of matching list items to skip
searchNoOptional case-insensitive search term; currently aliases name for list tools
statusNoOptional status filter for resources that expose status
deployedNoOptional function deployment filter: true or false
workspaceNoOptional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
schema_modeNoOptional dataset schema mode filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.136.0
    • addedInput schema / properties / deployed
      Added value: +{
+  "description": "Optional function deployment filter: true or false",
+  "type": "string"
+}
    • removedInput schema / properties / env
      Removed value: -{
-  "description": "Optional app environment for the current view",
-  "type": "string"
-}
    • changedInput schema / properties / fields / description
      Previous value: -"Optional top-level output fields"New value: +"Top-level output fields to include. Prefer only fields needed now; call again with more fields if needed."
    • removedInput schema / properties / id
      Removed value: -{
-  "description": "App id for detail, files, or version view",
-  "type": "string"
-}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum list items to return; use offset to continue",
+  "type": "integer"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional case-insensitive name substring filter for list tools",
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of matching list items to skip",
+  "type": "integer"
+}
    • addedInput schema / properties / schema_mode
      Added value: +{
+  "description": "Optional dataset schema mode filter",
+  "type": "string"
+}
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Optional case-insensitive search term; currently aliases name for list tools",
+  "type": "string"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Optional status filter for resources that expose status",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Optional type filter, for example provider type, transform trigger mode, or function language",
+  "type": "string"
+}
    • removedInput schema / properties / version
      Removed value: -{
-  "description": "App version for a version view",
-  "type": "integer"
-}
  2. Addedv0.135.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered. The description adds useful scope context by noting per-call workspace targeting without changing defaults, but it does not discuss pagination behavior or result characteristics beyond what the schema implies.

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 compact sentences, front-loaded with the core action and followed by the key targeting caveat. There is no wasted text.

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 read-only list tool with fully described parameters and no output schema, the description provides enough context to call it correctly, including the project scope and per-call workspace behavior. It could still mention pagination/filtering behavior or return-shape expectations more explicitly.

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 all parameters, including nested workspace fields, are already documented in the schema. The description briefly mentions the workspace shape and per-call behavior, but adds little semantics beyond the structured parameter descriptions, so baseline 3 applies.

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 states a specific verb and resource ("List hosted ontology-powered apps") and scopes it to the selected project. It is clear enough to distinguish this as a list operation, but it does not explicitly differentiate from nearby app-related siblings such as whodb_platform_app or whodb_platform_app_views.

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

Usage Guidelines2/5

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

It explains that workspace targeting is per-call and does not change defaults, but it gives no guidance on when to use this tool versus alternatives. There are no exclusions or decision rules for choosing between this and sibling app-listing/view tools.

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