Skip to main content
Glama
Sign In
bc-source-mcp

bc-source-mcp

by glachana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Refresh branch index

bc_refresh
Idempotent

Re-fetches a specified branch from upstream and re-indexes it. If no branch is given, sequentially refreshes all previously indexed branches.

Instructions

Re-fetches a branch from upstream and re-indexes it. If branch is omitted, refreshes every already-indexed branch sequentially.

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": "bc_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoSpecific branch to refresh, e.g. "w1-26". Omit to refresh all indexed branches.

Output Schema

NameRequiredDescriptionDefault
refreshedYes
errorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: describes re-fetch from upstream (write operation) and sequential refresh when branch omitted. Annotations already indicate idempotent and non-read-only, so description complements without contradiction.

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 sentences, front-loaded with action, no wasted words. Efficiently conveys all necessary information.

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?

With output schema present and simple tool (1 optional param), description provides complete context for agent to decide when to use. No gaps.

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% with branch description. Description adds meaning by specifying effect of omitting parameter (refresh all), which is not in schema.

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?

Description clearly states verb ('Re-fetches and re-indexes') and resource ('branch'). Distinguishes behavior when branch is specified vs omitted. Clearly distinct from siblings like bc_cache_status which only checks cache state.

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?

Explicitly says when to use (to refresh a specific branch or all indexed branches). Does not mention when not to use or compare to alternatives, but context is clear given sibling tool names.

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