Skip to main content
Glama

Gluecron

by com.gluecron
OverviewDiscussionsAdmin

gluecron_set_repo_secret

Create or replace one workflow secret on a repository, used in workflows as ${{ secrets.NAME }}. The name is saved upper-cased (cron_secret → CRON_SECRET); trailing spaces/newlines are removed from the value. The value is WRITE-ONLY: it is encrypted at rest and never returned, logged or audited — the result names the secret only. Pass expected_updated_at (the updated_at you last read) to update only if nobody changed it since: a newer value is never overwritten (error 'conflict'), a deleted secret is not re-created (error 'missing'). Setting the value it already has writes nothing (result 'unchanged'), so a retry is safe. Needs admin access to the repository and 'repo' scope. Audit-logged (name only). Returns {repository, name, created, result: 'created'|'updated'|'unchanged', updated_at}.

Input Schema

NameRequiredDescriptionDefault
nameYesSecret name: letters, digits, underscores; not starting with a digit
repoYesRepo name
ownerYesRepo owner — username or organisation slug
valueYesThe secret value (never echoed back)
expected_updated_atNoOptional ISO time: only update if the secret's updated_at is still this (from gluecron_list_repo_secrets)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / expected_updated_at
      Added value: +{
+  "description": "Optional ISO time: only update if the secret's updated_at is still this (from gluecron_list_repo_secrets)",
+  "type": "string"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false. The description adds substantial context: the value is write-only and encrypted at rest, never returned/logged/audited, the result names only the secret, retries are safe, conflict/missing errors are described, and permissions plus audit logging are stated.

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?

The description front-loads purpose and then covers value handling, concurrency, permissions, and return shape in compact, information-dense sentences. Every sentence earns its place with no 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?

For a complex mutation tool with minimal annotations and no output schema, the description fully covers write behavior, failure modes, required permissions, and return values. Nothing essential for correct invocation 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 coverage is 100%, so the baseline is 3. The description adds meaningful parameter semantics beyond the schema: the name is saved upper-cased, surrounding whitespace is stripped from the value, and expected_updated_at is explained as an optimistic-concurrency guard.

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 ('create or replace'), resource ('one workflow secret on a repository'), and integration context ('${{ secrets.NAME }}'). It is clearly distinguishable from siblings such as gluecron_delete_repo_secret and gluecron_list_repo_secrets.

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?

Explains concurrency usage via expected_updated_at and details behavior on conflict, missing, and unchanged outcomes. It also notes admin access and 'repo' scope. It lacks an explicit when-not or direct alternative comparison, but the operational context is clear.

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

All Gluecron 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