Skip to main content
Glama
clidey

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_secrets

Read-onlyIdempotent

List hosted project secret metadata and usage without exposing secret values. Filter by name or workspace for targeted access.

Instructions

List hosted project secret metadata and usage. Use name to filter by secret name when known.

This tool never returns secret values, redacted placeholders, or credential material. Authorization is enforced by the hosted platform. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

TableJSON 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. Addedv0.135.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world safety, but the description adds materially more: it explicitly guarantees no secret values, redacted placeholders, or credential material are returned, notes that authorization is enforced by the hosted platform, and explains that workspace targeting applies per-call without mutating defaults.

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?

Three tight sentences with the purpose and safety guarantee front-loaded; nothing is bloated. The middle sentence on `name` filtering lightly restates the schema description, which is the only minor redundancy.

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 10-parameter, all-optional list tool with no output schema, the description covers the two things an agent most needs: what is returned (metadata and usage) and the critical negative guarantee (no secret values). The shape of the returned metadata/usage is left unspecified, which is a small gap given the absence of an output schema.

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% across all 10 parameters, so the schema already carries the semantics. The description only adds a usage note for `name` ('when known'), which does not go beyond the schema's own substring-filter description; baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('List hosted project secret metadata and usage'), not a restatement of the tool name. It scopes the operation to hosted project secrets, which no sibling tool overlaps with, so an agent can identify it immediately.

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?

It says to use `name` when the secret name is known, which is a filtering hint rather than guidance on when this tool is the right choice. There is no statement of when-not to use it or what alternative exists for related credential operations.

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