Skip to main content
Glama

Darwin

by so.darwin
OverviewDiscussionsAdmin

List auth credentials

list_auth_credentials
Read-onlyIdempotent

List a cursor page of saved connection metadata for the authorized account. Continue with nextCursor as afterCursor until null. Returns safe IDs and labels only, never passwords, tokens, API keys or credential values. Selecting a saved credential does not grant new permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum saved credentials to return, up to 100.
afterCursorNoContinue after the previous response nextCursor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextCursorYes
credentialsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / actingAiId
      Removed value: -{
-  "description": "Authorized Darwin AI whose saved credential metadata to list.",
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "actingAiId"
-]
    • addedOutput schema / properties / credentials / items / properties / revision
      Added value: +{
+  "description": "Opaque revision for conditional revocation.",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+  "type": "string"
+}
    • changedOutput schema / properties / credentials / items / required
      Previous value: -[
-  "credentialId",
-  "provider",
-  "label",
-  "status",
-  "expiresAt",
-  "createdAt"
-]New value: +[
+  "credentialId",
+  "provider",
+  "label",
+  "status",
+  "expiresAt",
+  "createdAt",
+  "revision"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / afterCursor
      Added value: +{
+  "description": "Continue after the previous response nextCursor.",
+  "maxLength": 512,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9._-]+$",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum saved credentials to return, up to 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedOutput schema / properties / nextCursor
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 512,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9._-]+$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "credentials"
-]New value: +[
+  "credentials",
+  "nextCursor"
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, yet the description adds meaningful disclosure beyond them: it guarantees only safe IDs and labels are returned and that passwords, tokens, API keys and credential values are never exposed, and it clarifies that choosing a credential confers no new permission. For a security-sensitive listing tool this is exactly the behavior an agent needs.

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?

Three tight sentences, front-loaded with the core action and scoping, then pagination mechanics, then the safety guarantee. Every sentence carries distinct information with no repetition or filler.

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 an output schema exists, the description usefully characterizes the returned payload (safe IDs and labels only) and closes the pagination loop. Nothing needed to call or interpret this tool correctly is missing.

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 description coverage is 100%, so a 3 is the baseline. The description goes slightly further by tying the response field nextCursor to the afterCursor parameter, documenting the pagination handoff that the schema alone only implies.

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?

States a specific verb (List) and a precisely scoped resource (a cursor page of saved connection metadata for the authorized account). It is clearly distinguishable from the other list_* siblings (payment methods, threads, search history, act history) because it names credential metadata specifically.

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?

Gives concrete operational guidance: 'Continue with nextCursor as afterCursor until null' defines the pagination loop, and it clarifies that selecting a saved credential does not grant new permission. It does not, however, state when to prefer this over the sibling list tools, so it stops short of full when/when-not coverage.

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

All Darwin toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources