AgentPlaybooks

Check a secret without revealing it

get_secret_status

Read-onlyIdempotent

Check one named secret without decrypting it.

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": {
      "playbook_id": "<playbook_id>",
      "secret_name": "<secret_name>"
    },
    "name": "get_secret_status"
  }
}

Input Schema

Name	Required	Description	Default
`playbook_id`	Yes	UUID or GUID of the target playbook
`secret_name`	Yes	Exact vault secret name

Output Schema

Name	Required	Description	Default
`name`	Yes
`exists`	Yes
`reason`	No
`expires_at`	No
`next_steps`	No
`capabilities`	No
`allow_api_key_reveal`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds a genuine behavioral fact beyond them: the secret value is not decrypted, meaning no plaintext is exposed and no side effects on vault state occur. It stops short of describing what 'status' actually consists of, though an output schema exists to cover that.

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?

A single short sentence with the key constraint ('without decrypting it') placed where it is read first. Nothing is redundant with the title or wasted.

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 two-parameter read tool with full schema coverage, an output schema, and complete annotations, the description supplies the one non-obvious behavioral fact (no decryption). The remaining gap is routing guidance against use_secret, which would make the definition self-sufficient.

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%, with both required parameters ('playbook_id' as UUID/GUID, 'secret_name' as exact vault name) documented inline. The description adds no further parameter meaning, so the baseline of 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 ('Check one named secret') plus a distinctive scope qualifier ('without decrypting it'), which separates it from write-oriented siblings like use_secret_write. It does not name or contrast with use_secret, the closest alternative, so full sibling differentiation is missing.

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?

Usage is only implied: the 'without decrypting' clause suggests this is the non-invasive status/metadata check rather than the tool that retrieves or consumes the value. There is no explicit statement of when to pick this over use_secret, nor any prerequisite guidance about playbook context.

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

All AgentPlaybooks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?