Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_secret_references

Read-onlyIdempotent

Fetch secret references while keeping authentication config and resolved values hidden. Filter by manager type, tags, or name to find the UUID or slug for later use.

Instructions

List Secret References without returning authentication configuration or resolved secret values. Filter by manager type, tags, or name and use a returned UUID or slug with get_secret_reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoReturn references matching these tags
searchNoSearch references by name
page_sizeNoReferences per page, from 1 to 100; defaults to 20
current_pageNoZero-based page number; defaults to 0
manager_typeNoFilter by external secret manager: aws_sm, azure_kv, or hashicorp_vault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.5
    • addedInput schema / properties / page_size / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / page_size / minimum
      Removed value: -1
  2. Addedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's added value is the explicit guarantee that authentication configuration and resolved secret values are not returned. This is useful behavioral context beyond the annotations and helps set expectations for callers.

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 sentences, no fluff, and the most important behavioral constraint ('without returning authentication configuration or resolved secret values') is front-loaded. The filter options and follow-up usage are stated efficiently.

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?

Given the rich annotations, fully described schema, and presence of an output schema, the description is complete. It adds the necessary context about what the list excludes and how to proceed to a detailed reference, leaving no critical gap for correct invocation.

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 schema already documents all five parameters. The description adds a compact mapping of the main filter dimensions (manager type, tags, name) and notes the output contains UUIDs/slugs, providing extra semantic glue beyond raw parameter descriptions.

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 clearly states the action: 'List Secret References' while explicitly excluding authentication configuration and resolved secret values. It also distinguishes itself from the sibling get_secret_reference by naming that tool as the follow-up for retrieving a specific reference.

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?

The description gives concrete filtering guidance (manager type, tags, name) and a clear next-step instruction to use a returned UUID or slug with get_secret_reference. It does not explicitly state when not to use this tool, but the context strongly implies it is for discovery/listing rather than fetching full secret details.

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