Skip to main content
Glama

get_config

Read-onlyIdempotent

Fetch a GitHub repository's current MergeQueue YAML configuration, optionally with recent change history, to review queue settings or audit configuration updates.

Instructions

Current MergeQueue YAML config of a repo, optionally with change history.

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_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
max_charsNo
history_endNoYYYY-MM-DD
history_startNoYYYY-MM-DD
include_historyNoAlso return recent config changes (who/when/diff).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that the payload is YAML and that change history is optional, but says nothing about auth needs, truncation via max_chars, or what the history entries contain beyond the schema's parenthetical.

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?

A single front-loaded clause with zero waste; the resource and its optional mode come first. It is a noun phrase rather than a sentence, which is terse but still unambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter read tool with no output schema and no required params, the description is serviceable but leaves gaps: whether output is truncated when max_chars is exceeded and how the history range interacts with include_history. An agent could call it correctly, but not confidently predict the response shape.

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 coverage is 83%, so the schema largely documents org, repo, history_start/history_end, include_history and max_chars itself. The description echoes include_history ('optionally with change history') but adds no meaning to max_chars truncation or the org/repo fallback rule.

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 resource ('Current MergeQueue YAML config of a repo') and scope ('current', optionally with history), which distinguishes it from the mutating sibling update_config. The retrieval verb is only implied ('Current ... config of a repo'), so it stops short of a full 5.

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?

There is no statement of when to call this instead of update_config, get_analytics, or get_queue_stats, and no prerequisites. 'Optionally with change history' hints at a variant mode, but that is usage of a parameter, not tool-selection guidance.

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