Skip to main content
Glama

Mostly Right

by md.mostlyright
OverviewDiscussionsAdmin

List the source credentials this workspace holds

list_source_credentials
Read-onlyIdempotent

Lists named secret metadata and saved workspace connections without secret values. Pass dataset_id to check dataset grants. Follow connections.next_offset with connection_offset to read another bounded page. Returns credentials, connections (status, safe items, grants_status), and a structured source_credentials setup request for the chat UI. Stored or active means enrolled, not a verified provider login. If setup or dataset access is missing, stop and ask the person to use the secure setup card or settings links; never request a key, password, private key or verification code in chat. After the person returns, call this again before resuming. Connection recipes use connection_id, version_digest and source_parameters; values never belong in a recipe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idNo
connection_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / connection_offset
      Added value: +{
+  "maximum": 500,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / dataset_id
      Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantially more: no secret values are returned, 'stored or active means enrolled, not a verified provider login', pagination bounded by next_offset, and an explicit prohibition on requesting keys/passwords/codes in chat.

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?

Purpose is front-loaded and every sentence carries operational content, but the closing sentence about connection recipes, connection_id, version_digest and source_parameters is dense jargon that is only loosely tied to listing credentials.

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 no output schema, the description usefully sketches the return shape (credentials, connections with status/safe items/grants_status, structured setup request) and covers paging and safety. It is close to complete, though the setup-request semantics remain somewhat opaque.

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 0%, so the description must carry parameter meaning. It explains dataset_id's role (check dataset grants) and connection_offset's role and linkage to connections.next_offset for paging, covering both parameters usefully, though format/type details remain in the schema.

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?

States a specific verb and resource: 'Lists named secret metadata and saved workspace connections without secret values.' The scope (metadata only, no secret values) is explicit and no sibling tool overlaps this resource, though it does not name a sibling to contrast with.

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?

Gives explicit conditions: pass dataset_id to check dataset grants, follow connections.next_offset with connection_offset for another page, and stop to route the person to the secure setup card if setup or dataset access is missing. It even specifies the re-entry behavior ('call this again before resuming').

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

All Mostly Right toolsInspect
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