Skip to main content
Glama
knaisoma

data-olympus MCP server

KB Resolve Pending

kb_resolve_pending
Destructive

Resolve pending proposals by approving with optional edits or rejecting. Allows operator override of secret-scan gate for false positives.

Instructions

Resolve a pending proposal: approve (optionally with edited text) or reject. Approval commits + enqueues for push.

override_secret_scan: operator-only override of the secret- scanning gate (issue #71). When True and the resolved postimage matches a credential pattern, the commit proceeds anyway instead of being rejected rejected_secret_detected, and the audit event records that the override was used. Use only after confirming the flagged content is NOT a real credential.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
decisionYesResolution decision: approve or reject.
pending_idYesPending proposal id to resolve.
edited_textNoOptional replacement postimage used when approving.
agent_identityNoHuman-readable agent identity for audit events.operator
source_sessionNoStable id of the agent session making the call.operator-resolve
override_secret_scanNoOperator override for false-positive secret-scan matches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond annotations (destructiveHint=true, etc.), the description explains the override behavior with specific consequences and security considerations, adding significant value.

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?

Five sentences, with a clear first sentence summarizing the main action. The detailed explanation for override_secret_scan is necessary and well-organized. Slight redundancy but overall efficient.

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?

The description covers behavior, side effects, and security considerations adequately. Given the presence of an output schema, it is sufficiently complete.

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 covers all parameter descriptions (100%). The description adds extra context for override_secret_scan, explaining its purpose and usage. This exceeds the baseline of 3.

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 clearly states the tool resolves a pending proposal with specific actions (approve or reject) and the effect (commit + enqueue for push). This distinguishes it from sibling tools like kb_list_pending and kb_propose_edit.

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?

Provides clear context for using override_secret_scan and implies when to use the tool. Does not explicitly state when not to use it, but overall guidance is strong.

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/knaisoma/data-olympus'

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