agentic-sdlc-mcp

Get Repository Context

repo_context

Read-onlyIdempotent

Reads GitHub repository baseline context including metadata, README, tech stack, open issues, and PRs to understand the codebase before planning SDLC work items.

Instructions

Read baseline context for a GitHub repository, including metadata, README summary, package.json summary, tech stack, common scripts, workflow file names, governance signals, agent instruction file summaries, open issues, and open PRs.

Use this tool at the start of any SDLC workflow to understand the codebase before planning or creating work items.

Args:

owner (string?): GitHub org or user. Defaults to GITHUB_OWNER env var.
repo (string?): Repository name. Defaults to GITHUB_REPO env var.
includeReadme (boolean): Include truncated README. Default: true.
includePackageJson (boolean): Include package.json summary, detected package manager, tech stack, and common scripts. Default: false.
includeWorkflows (boolean): Include .github/workflows/*.yml file names. Default: false.
includeAgentInstructions (boolean): Include summaries of AGENTS.md/CLAUDE.md if present. Default: false.
includeGovernance (boolean): Include whether a CODEOWNERS file exists. Default: false.
includePolicy (boolean): Include validated repository policy and provenance. Default: false.
includeOpenIssues (boolean): Include recent open issues. Default: false.
includeOpenPRs (boolean): Include open pull requests. Default: false.
issueLimit (number): Max open issues to fetch. Default: 20, max: 100.
prLimit (number): Max open PRs to fetch. Default: 20, max: 100.
maxReadmeChars (number): Max README characters before truncation. Default: 3000.
maxInstructionChars (number): Max characters per agent instruction file summary. Default: 1000.

Returns: Markdown summary of the repository context, plus structured content. Missing files (README, package.json, agent instructions) degrade gracefully rather than failing the whole call.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	No	GitHub repo name. Falls back to GITHUB_REPO env var.
`owner`	No	GitHub owner (org or user). Falls back to GITHUB_OWNER env var.
`prLimit`	No	Max number of open PRs to fetch when includeOpenPRs is true. Default: 20, max: 100.
`issueLimit`	No	Max number of open issues to fetch when includeOpenIssues is true. Default: 20, max: 100.
`includePolicy`	No	Include the validated .agentic-sdlc.yml policy summary, rule IDs, digest, and source ref/SHA.
`includeReadme`	No	Include a truncated README summary.
`includeOpenPRs`	No	Include a list of open pull requests (up to 20).
`maxReadmeChars`	No	Max README characters before truncation. Default: 3000.
`includeWorkflows`	No	Include `.github/workflows/*.yml` file names (names only, not permissions -- use workflow_permissions_audit for that).
`includeGovernance`	No	Include lightweight governance signals (currently: whether a CODEOWNERS file exists). For full branch protection details, use branch_protection_status.
`includeOpenIssues`	No	Include a list of recent open issues (up to 20).
`includePackageJson`	No	Include a package.json summary, detected package manager, tech stack, and common scripts.
`maxInstructionChars`	No	Max characters per agent instruction file summary before truncation. Default: 1000.
`includeAgentInstructions`	No	Include summaries of agent instruction files (AGENTS.md, CLAUDE.md) if present at the repo root.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`policy`	No
`topics`	Yes
`openPRs`	No
`scripts`	No
`fullName`	Yes
`language`	Yes
`pushedAt`	Yes
`techStack`	No
`workflows`	No
`governance`	No
`openIssues`	No
`visibility`	Yes
`description`	Yes
`policyDigest`	No
`policyErrors`	No
`defaultBranch`	Yes
`policySources`	No
`readmeSummary`	No
`trustBoundary`	No
`packageManager`	No
`policyWarnings`	No
`openIssuesCount`	Yes
`stargazersCount`	Yes
`agentInstructions`	No
`appliedPolicyRules`	No
`packageJsonSummary`	No
`promptInjectionWarnings`	No

Tool Definition Quality

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds useful behavioral details: returns Markdown summary plus structured content, degrades gracefully for missing files. Does not contradict annotations.

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?

Well-structured: one-sentence purpose, usage guidance, parameter list, return behavior. While somewhat long given 14 parameters, the format is clear and front-loaded. No wasted sentences, but could be slightly more concise.

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?

Given the tool's complexity (14 parameters, output schema exists, annotations present), the description is complete. It covers purpose, usage, parameter semantics (via schema), behavior (graceful degradation), and return value. No missing pieces.

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%, so baseline is 3. Description summarizes each parameter in the 'Args' section but adds little beyond what the schema already provides (defaults, behavior). Some parameters get extra context (e.g., includeWorkflows mentions alternative tool), but overall limited added value.

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 begins with a specific verb and resource: 'Read baseline context for a GitHub repository'. It clearly enumerates what the context includes (metadata, README, package.json, etc.), and distinguishes from sibling tools like plan_from_context, which focus on planning rather than reading.

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 states when to use: 'at the start of any SDLC workflow to understand the codebase before planning or creating work items'. Does not explicitly list when not to use or name alternative tools for specific subtasks, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SakuraCianna/agentic-sdlc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server