Symbioza

List your saved secrets (metadata only, never values)

listSecrets

Read-onlyIdempotent

List the secret sets saved on THIS account — metadata only (names, types and variable names); values are never returned, to anyone, by this or any other tool (a job that attaches a set is what receives them). Each row carries id, name, type (huggingface, object-storage, wandb or custom), provider (object storage only), fields (the environment variable NAMES the set injects) and status — metadata only, never a value, and only this account's sets. Attach a set to a job with the spec's secrets, by name (or by id). Credentials are saved by the user at https://symbioza.dev/app/secrets — never pasted into chat and never put in env. Call it again after the user says they saved a set: continue only if it is listed. Free, books nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, access_required, secret_conflict, no_compute, unavailable, refused
`note`	No
`count`	No
`action`	No	The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, add_access, relax_spec_or_retry, retry_later, contact_support
`reason`	No	Why, in a customer-safe sentence
`secrets`	No	This account's saved secret sets: metadata only, never a value
`rejected`	No	Present and true when the call was refused; nothing was booked or charged
`manageUrl`	No	Where the user adds, rotates or deletes a saved set
`supportedImages`	No	On an unverified-image refusal: the images the door accepts

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 5, 2026
- removedInput schema / properties / authKey
```
Removed value: -{
-  "description": "Usually omit this. The customer door — the OAuth-signed-in HTTPS connector at https://symbioza.dev/mcp — authenticates the session itself, so no key is passed per call. Only a self-hosted or test transport passes a key here.",
-  "type": "string"
-}
```
- changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```
- addedOutput schema / properties / count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / count / minimum
```
Added value: +0
```
- changedOutput schema / properties / count / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / secrets / description
```
Previous value: -"This account's saved secret sets: names and types only"New value: +"This account's saved secret sets: metadata only, never a value"
```
- changedOutput schema / properties / secrets / items / additionalProperties
```
Previous value: -{}New value: +false
```
- addedOutput schema / properties / secrets / items / properties / fields / items / pattern
```
Added value: +"^[A-Za-z_][A-Za-z0-9_]{0,127}$"
```
- addedOutput schema / properties / secrets / items / properties / id / description
```
Added value: +"The set's id (sec_…); spec.secrets accepts it in place of the name"
```
- addedOutput schema / properties / secrets / items / properties / id / pattern
```
Added value: +"^sec_[A-Za-z0-9_-]{22}$"
```
- removedOutput schema / properties / secrets / items / properties / lastUsedAtMs
```
Removed value: -{
-  "type": "number"
-}
```
- addedOutput schema / properties / secrets / items / properties / name / description
```
Added value: +"The set's name: what spec.secrets references"
```
- addedOutput schema / properties / secrets / items / properties / name / pattern
```
Added value: +"^[a-z0-9][a-z0-9_-]{0,62}$"
```
- addedOutput schema / properties / secrets / items / properties / provider / description
```
Added value: +"Object storage only: which kind"
```
- addedOutput schema / properties / secrets / items / properties / provider / enum
```
Added value: +[
+  "s3",
+  "r2",
+  "s3-compatible"
+]
```
- addedOutput schema / properties / secrets / items / properties / status / const
```
Added value: +"ready"
```
- addedOutput schema / properties / secrets / items / properties / type / enum
```
Added value: +[
+  "huggingface",
+  "object-storage",
+  "wandb",
+  "custom"
+]
```
AddedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: values are never returned by this or any other tool, credentials are created out-of-band at a URL rather than passed in chat or env, and the call is free and books nothing. This is meaningful extra behavioral disclosure.

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?

Front-loaded with the core action and scope, and most sentences carry distinct information (row fields, attach path, credential URL, re-check flow). It repeats 'metadata only, never a value' roughly three times, which costs some density but does not bury the lead.

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?

With an output schema present the description need not explain return values, and annotations cover the safety profile, so what remains is workflow context — which it supplies (how to attach a set, where credentials come from, verifying after creation). Complete enough to call correctly; only the repetition is a minor blemish.

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?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline is 4. The description instead enumerates the returned row fields, which is beyond the burden of a parameterless tool.

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 names a specific verb and resource (list the secret sets saved on THIS account) and immediately bounds the scope to metadata only, distinguishing it from any tool that would return values. An agent knows exactly what it gets back (id, name, type, provider, fields, status) without opening the schema.

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?

It gives real usage context: attach a set to a job via the spec's secrets, and re-call after the user reports saving a set, continuing only if it is listed. No sibling alternative exists to route against, so the lack of explicit 'use X instead' is not a gap, but it stops short of a full when/when-not treatment.

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

All Symbioza tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.