seekrit — secrets for agents

list_lease_targets

Read-onlyIdempotent

List the registered temporary-access targets — the databases (Postgres, MySQL, …) against which short-lived credentials can be minted on demand instead of storing a standing password. Use it to see what can be leased before minting one (create_pg_lease / create_mysql_lease run on the LOCAL crypto plane), and see list_leases for what has actually been issued. Returns [{ id, orgId, provider, name, config, createdAt }], where provider names the kind of target (postgres, mysql, …) and config is non-secret connection settings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`org`	No	Organization slug or id. Omit it when the credential can reach exactly one org — that org is used automatically. With several, the error names every slug you may pass; list them yourself with list_orgs.

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 destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: it clarifies that config is non-secret, what provider means, and what fields will appear in the result. It does not go into auth or rate limits, but with rich annotations the added context is sufficient.

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?

The description is compact and front-loaded: first the resource and purpose, then usage guidance, then return shape. Every sentence earns its place, and there is no wasted or repetitive phrasing. The parenthetical clarifications are useful rather than distracting.

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?

Even though there is no output schema, the description explicitly lists the returned fields and clarifies the meaning of provider and config. Combined with the fully documented optional org parameter and strong annotations, nothing essential is missing for an agent to select and invoke this tool correctly.

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?

The input schema has one optional org parameter with full description coverage, including behavior when omitted and when multiple orgs are reachable. The tool description itself adds no param-specific meaning, but the schema already documents the parameter thoroughly, so the baseline of 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 the registered temporary-access targets.' It explains what those targets are (databases for minting short-lived credentials) and differentiates itself from list_leases by describing the returned object shape and the relationship to lease creation. This is unambiguous and immediately distinguishes it from sibling tools.

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

Usage Guidelines5/5

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

The description explicitly says to use this tool to see what can be leased before minting one, and directs users to list_leases for what has actually been issued. It also flags that create_pg_lease/create_mysql_lease run on the local crypto plane, which prevents the agent from expecting them as sibling MCP tools. This is clear when-to-use guidance with relevant alternatives.

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

All seekrit — secrets for agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools target a distinct resource and action, and many descriptions explicitly call out their near neighbors (list_envs vs list_env_groups vs list_group_envs). The main ambiguity is the three-way env/group listing cluster and the partial overlap between list_orgs and whoami, but the descriptions largely mitigate misselection.

Naming Consistency4/5

Snake_case verb_noun naming dominates (list_*, create_*, delete_*, revoke_*, rename_*), and the kms_ prefix is used consistently. A few outliers like audit, billing, whoami, signup, get_started, local_tool_for, and setup_local_crypto break the strict pattern, but they are still readable and no camelCase or chaotic mixing is present.

Tool Count2/5

40 tools is far above the 25-tool threshold and creates a heavy surface for an agent to navigate. The broad domain of apps, groups, envs, secrets, members, tokens, KMS, and leases partially justifies the size, but several list/delete/revoke families could be consolidated.

Completeness3/5

The set covers control-plane lifecycle well for apps, groups, and invitations, and provides solid list/delete/revoke coverage for envs, branches, tokens, leases, and KMS. However, create operations for envs, branches, tokens, and leases, plus all secret value reads/writes, are deliberately delegated to the local crypto plane; local_tool_for and setup_local_crypto help bridge the gap, but the server is not standalone-complete.

Resources

Need Help?