Secret Store

Search secret keys

search_secrets

Read-onlyIdempotent

Find where a key lives across the projects and environments this token can reach: a substring (database) or a pattern with * (NEXT_PUBLIC_*). Names only, never values. Requires projects:read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_secrets"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Substring of the key, case-insensitive, or a pattern with *
`project`	No	Limit the search to one project

Output Schema

Name	Required	Description
`query`	Yes
`matches`	Yes
`truncated`	No	More matches exist than are listed
`projectsSearched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context: results are scoped to what the token can reach, values are never returned, and a specific permission (projects:read) is required. It does not mention result caps or pagination.

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, zero filler, with the scope and the names-not-values constraint front-loaded before the permission note. Every clause carries information an agent needs.

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?

An output schema exists, so return values need not be explained, and both parameters are documented. The remaining gap is operational detail such as result limits or pagination behavior for broad patterns, which matters given the cross-project scope.

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 coverage is 100%, and the schema already documents both query (substring or * pattern) and project (limit to one project). The description's examples (database, NEXT_PUBLIC_*) illustrate the shape but add little beyond the field descriptions, so the baseline of 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?

Specific verb and resource ("Find where a key lives") plus a precise scope ("across the projects and environments this token can reach"). The phrase "Names only, never values" separates it from get_secret/set_secret, and the pattern examples make the search semantics concrete.

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?

Clear context for use: searching across many projects/environments rather than a single known key, with the projects:read prerequisite stated. It stops short of naming an explicit alternative (e.g., get_secret for values), so the when-not guidance is implied by "names only, never values" rather than stated.

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

All Secret Store 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?