Skip to main content
Glama

sumo_qa_ingest_knowledge_pack

Add or replace team QA standards and rules from local native files into your knowledge pack. Validates content and writes a normalized copy for project or global use.

Instructions

Adds or replaces team QA knowledge/standards/rules from a local native file.

Accepts a path to a native sumo-qa file or a directory of them: principles.md, techniques.md, classifications.md, approaches.md, a standards-pack *.yaml, or change_rules.yaml. Validates the content and writes a normalized copy into a user-writable pack. The scope argument selects where it lands: 'project' (/.sumo-qa, the current repo only) or 'global' (the user data dir, every repo) — the right scope is a user choice worth confirming. Loader precedence is env var > project > global > bundled > repo root.

A PDF / PPTX / URL or any other non-native source is not parsed here; it returns an unsupported_source result that routes through the sumo-qa-suggesting-external-skill flow to convert the source to markdown, which is then re-ingested with an explicit content_type.

Common natural-language phrasings that map to this tool: "add this to the knowledge base", "replace our principles", "load our team standards pack", "use these change rules", "ingest this QA pack".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoproject
sourceYes
content_typeNo
Behavior4/5

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

Annotations (all false) are minimal. The description adds value by explaining validation, normalized copy writing, loader precedence, and the unsupported_source result. However, it could detail more about return values beyond error cases.

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 with front-loaded main action, detailed paragraphs, and even natural-language phrasings. Slightly verbose in places (e.g., loader precedence details) but every sentence serves a purpose.

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 no output schema and sparse annotations, the description covers all necessary aspects: inputs, behavior, edge cases, and alternative flows. It fully equips the agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully explains all three parameters: source (path), scope (project vs global with reasoning), and content_type (for non-native conversion). This compensates completely for the missing schema descriptions.

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?

The description starts with a clear verb+resource statement: 'Adds or replaces team QA knowledge/standards/rules from a local native file.' It specifies accepted file types and distinguishes from non-native sources, making it distinct from sibling tools like load_* which are read-only.

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

Usage Guidelines5/5

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

Explicitly states when to use (for native sumo-qa files) and when not to use (PDF/PPTX/URL), directing to an alternative flow via sumo_qa_suggesting_external_skill. Also clarifies scope choice and loader precedence, providing comprehensive guidance.

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

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/sumithr/sumo-qa'

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