Skip to main content
Glama

Gluecron

by com.gluecron
OverviewDiscussionsAdmin

gluecron_update_repo

Destructive

Update repository description / visibility / default_branch. Requires 'admin' access on the repo (owner, org owners/admins, admin collaborators) and 'repo' scope. Returns {ok: true}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesRepo name
ownerYesRepo owner username
automationNoPer-repo automation dials, same keys as Settings → Automation: ai_review_mode, pr_triage_mode, issue_triage_mode, auto_merge_mode, ci_autofix_mode, auto_repair_mode, auto_issues_mode, doc_drift_mode, merge_train_mode. Values: off | suggest | auto (merge_train_mode runs only on auto). Only the keys given change.
is_privateNoSet visibility (optional)
descriptionNoNew description (optional)
default_branchNoSet default branch (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / automation / description
      Previous value: -"Per-repo automation dials, same keys as Settings → Automation: ai_review_mode, pr_triage_mode, issue_triage_mode, auto_merge_mode, ci_autofix_mode, auto_repair_mode, auto_issues_mode, doc_drift_mode. Values: off | suggest | auto. Only the keys given change."New value: +"Per-repo automation dials, same keys as Settings → Automation: ai_review_mode, pr_triage_mode, issue_triage_mode, auto_merge_mode, ci_autofix_mode, auto_repair_mode, auto_issues_mode, doc_drift_mode, merge_train_mode. Values: off | suggest | auto (merge_train_mode runs only on auto). Only the keys given change."
  2. Changed1 schema field changed
    • addedInput schema / properties / automation
      Added value: +{
+  "description": "Per-repo automation dials, same keys as Settings → Automation: ai_review_mode, pr_triage_mode, issue_triage_mode, auto_merge_mode, ci_autofix_mode, auto_repair_mode, auto_issues_mode, doc_drift_mode. Values: off | suggest | auto. Only the keys given change.",
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is known. The description adds genuinely useful non-schema context: the exact access level required, the OAuth scope, and the return shape {ok: true}. It does not spell out what makes the operation destructive (e.g., visibility changes), but the auth/return detail is solid added value.

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?

Two tightly packed sentences with the action front-loaded and prerequisites/return value following. No filler, every clause earns its place.

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 destructive mutation with full schema coverage and annotation-declared safety profile, the description covers the essential gaps: auth requirements and return shape. It is slightly incomplete in not mentioning the automation dials the tool can also modify, but no output schema exists and the return is disclosed.

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%, including detailed docs for the nested 'automation' object, so the schema carries the parameter burden. The description restates three of the fields (description, visibility, default_branch) without adding format or constraint detail beyond the schema, which is the expected baseline.

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 (update) and resource (repository) plus the concrete fields it can change, which distinguishes it from delete_repo, fork_repo, and other sibling repo tools. It omits the 'automation' dial capability that the schema exposes, so the purpose is slightly narrower than the tool actually is.

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?

The description states the prerequisite (admin access on the repo and 'repo' scope) but gives no guidance on when to choose this tool versus alternatives or when not to use it. Usage context is implied by the 'update repository settings' framing rather than stated.

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