Skip to main content
Glama

Read my effective repository config

get_repo_config
Read-onlyIdempotent

Read the effective .sinatrarc, provenance and your own override for a connected repository. Any workspace member.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>"
    },
    "name": "get_repo_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesThe repository id from get_workspace.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuine value by disclosing the access requirement ('Any workspace member') and the composite nature of the result ('effective' config plus provenance plus personal override). It stops short of describing result shape or what happens when no override or .sinatrarc exists.

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?

Two short sentences, with the object of the read front-loaded before the access note. There is no filler, though the trailing fragment 'Any workspace member.' is terse enough to read slightly ambiguously as a permission statement.

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 two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, access scope, and what the returned config comprises. Only the return format and the no-override/no-file edge case are left unstated, which is a minor gap.

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% and both parameters carry their own descriptions, including where to obtain each id (get_workspace, whoami). The description adds no additional meaning about the identifiers or their interaction, so the schema does the work and the baseline of 3 applies.

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?

The description gives a specific verb (Read) and a specific resource (the effective .sinatrarc, provenance, and the caller's own override for a connected repository), which is far more precise than the title alone. It does not name sibling tools such as preflight_repo_config or set_repo_override, so the differentiation is implied rather than stated.

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 clause 'Any workspace member' tells the agent who may call it and 'for a connected repository' scopes the precondition, which is useful context. However, there is no explicit when-to-use versus when-not guidance and no pointer to alternatives like preflight_repo_config for validation or set_repo_override for mutation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources