Skip to main content
Glama
Sign In
ThumbGate

ThumbGate

by IgorGanapolsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get Branch Governance

get_branch_governance
Read-only

Retrieve the active branch and release governance state to see which actions are permitted. Use this to avoid branch-based mistakes before executing commands.

Instructions

Return the active branch and release governance state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_branch_governance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.23.1
  2. Removedv1.21.2
  3. Addedv1.16.9

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, and description aligns with 'Return'. No additional behavioral context beyond the obvious read operation, which is acceptable given annotation coverage.

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?

Single sentence of 10 words, efficiently conveys purpose with no waste. Ideal conciseness.

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?

Minimal but complete for a simple read-only tool with no parameters or output schema. Could be more explicit about return structure, but sufficient given low complexity.

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?

No parameters exist, and schema description coverage is 100%. Description does not need to add param info; baseline 4 applies per guidelines.

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?

Description clearly states the tool returns active branch and release governance state, with a specific verb and resource. Distinguishes from sibling 'set_branch_governance' but could add more detail on what 'release governance state' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like 'set_branch_governance' or other governance tools. Implied usage from name, but missing explicit context.

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

Deploy Server

Other Tools