Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_server_infoA

Return the server identity, the COSO framework it covers, and the mandatory disclaimer.

list_componentsA

List the five components of the COSO Internal Control—Integrated Framework (ICIF-2013).

list_principlesA

List the 17 principles of the COSO ICIF-2013, optionally filtered to a single component.

get_principleC

Return a single COSO principle by framework number or slug, including its paraphrased points of focus.

get_componentA

Return a single COSO component by id, with its principles.

list_objective_categoriesA

List the three COSO objective categories (operations, reporting, compliance).

list_assertionsA

List the assertions used to frame control objectives: completeness, existence/occurrence, accuracy, valuation, obligations/rights, presentation/disclosure.

create_engagementA

Create a new internal-control review engagement. Returns the engagement id used by all later tools.

get_engagementC

Return an engagement by id.

list_engagementsA

List all engagement ids and titles.

add_scope_itemC

Add a significant account/process to the review scope, with its objective category and assertions.

list_scope_itemsC

List the scope items for an engagement.

register_riskC

Register a risk to objectives, with likelihood, assertions, related COSO principles and a fraud flag.

list_risksC

List the risks registered for an engagement.

register_controlC

Register a key control with its type, frequency, linked risks, assertions and COSO principles.

list_controlsC

List the controls registered for an engagement.

get_audit_logC

Return the append-only audit events recorded for an engagement.

compute_sample_sizeB

Recommend a sample size for a control from its frequency, risk and population size, with a documented rationale.

create_populationB

Register the population for a control — either an explicit item list or a declared size. Bounded to 10000 items.

list_populationsC

List the populations registered for an engagement.

select_sampleB

Select a reproducible sample from a population. Seeded (deterministic) for random/systematic/haphazard; targeted takes explicit references. Records the method, seed and references.

record_test_resultC

Record attribute-level outcomes (pass/fail/na) for a tested sample, with an optional conclusion.

list_test_resultsC

List the test results recorded for an engagement.

note_exceptionB

Record an exception identified during testing, with root cause, impact and any compensating control.

list_exceptionsC

List the exceptions recorded for an engagement.

assemble_workpaperC

Assemble a Markdown control-testing workpaper from the control, its risks, population, sample, test results and exceptions.

list_workpapersC

List the workpapers assembled for an engagement.

get_workpaperC

Return a workpaper including its rendered Markdown.

add_review_noteC

Add a reviewer note to a workpaper.

resolve_review_noteC

Mark a review note resolved on a workpaper.

sign_offB

Record a preparer or reviewer sign-off. Warns (does not block) if the same person prepared and reviewed.

get_activity_logB

Return the append-only activity log for an engagement, plus a Markdown rendering.

classify_deficiencyB

Classify a control deficiency as deficiency / significant deficiency / material weakness from likelihood × magnitude (escalates for a pervasive control).

list_deficienciesC

List the deficiencies recorded for an engagement.

aggregate_deficienciesC

Group related deficiencies by control, flag combinations that may aggregate, and report the overall severity.

assess_principleC

Report data-driven coverage indicators for one COSO principle (controls, risks and deficiencies mapped to it).

assess_componentB

Report coverage indicators for one COSO component, aggregating its principles.

framework_integration_checkB

Check that all five COSO components have some recorded coverage and that principles are addressed.

generate_reportB

Generate a Markdown internal-control review report: scope, risks, controls, testing, workpapers, deficiencies and COSO coverage.

Prompts

Interactive templates invoked by user choice

NameDescription
scope-reviewDraft the scope of a COSO internal-control review: objectives, significant accounts/processes, period and materiality.
assess-riskIdentify and analyze risks to objectives (including fraud) as the basis for selecting controls (COSO principles 6–9).
build-control-matrixTurn risks into a key-control matrix with type, frequency, owner and assertions (COSO principles 10–12).
draft-test-workpaperDraft a design/operating-effectiveness test workpaper with sample selection, procedures, results and conclusion.
evaluate-deficienciesClassify deficiencies by likelihood and magnitude, aggregate related deficiencies, and plan remediation (COSO principle 17).

Resources

Contextual data attached and managed by the client

NameDescription
icif-2013The full COSO Internal Control—Integrated Framework reference: components, principles, points of focus and objective categories.

TDQS

B3/5.0

Scored across 39 tools

Disambiguation4/5

Most tools map to a clearly distinct resource+action in the audit lifecycle (engagement, scope, risk, control, population, sample, test result, exception, workpaper, deficiency, report). The main overlap is get_audit_log vs get_activity_log, both described as append-only per-engagement logs, and the classify/aggregate/list_deficiencies trio requires reading descriptions to separate. Overall boundaries are clear enough that an agent can select correctly.

Naming Consistency4/5

Nearly all tools follow a consistent snake_case verb_noun pattern (create_engagement, register_risk, select_sample, list_exceptions). Deviations are minor: sign_off is verb-only, framework_integration_check puts the verb last, and assessment tools use assess_/classify_/aggregate_ prefixes that still read consistently.

Tool Count2/5

39 tools is heavy for a single MCP server, and the surface is inflated by many near-duplicate list_* tools (list_risks, list_controls, list_scope_items, list_populations, list_test_results, list_exceptions, list_workpapers, list_deficiencies) that could be one parameterized list endpoint. Each tool is individually defensible for a full audit lifecycle, but the set is larger than the workflow strictly requires.

Completeness4/5

The surface covers the whole engagement lifecycle end-to-end: setup, scoping, risk/control registration, sampling, testing, exceptions, workpapers, review notes, sign-off, deficiency classification, COSO coverage assessment, and reporting. Gaps are minor: there are no update/delete operations for engagements, risks, controls, or scope items, so corrections must be appended rather than amended.

Maintenance

ActivityNo data
ResponsivenessOutdated data