Skip to main content
Glama

elenchus_update_role_config

Update role enforcement settings including strict mode, minimum compliance score, and verifier/critic alternation requirement to control code verification behavior.

Instructions

Update role enforcement configuration. Can enable strict mode, change minimum compliance score, or toggle role alternation requirement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID
strictModeNoReject non-compliant rounds
minComplianceScoreNoMinimum compliance score (0-100)
requireAlternationNoRequire verifier/critic alternation

Implementation Reference

  • Handler function for the elenchus_update_role_config tool. Calls the core updateRoleConfig function with sessionId and optional config fields (strictMode, minComplianceScore, requireAlternation), then returns the updated config.
    export async function updateRoleConfigTool(
      args: z.infer<typeof UpdateRoleConfigSchema>
    ): Promise<object | null> {
      const config = updateRoleConfig(args.sessionId, {
        strictMode: args.strictMode,
        minComplianceScore: args.minComplianceScore,
        requireAlternation: args.requireAlternation
      });
    
      if (!config) return null;
    
      return {
        sessionId: args.sessionId,
        updated: true,
        newConfig: config
      };
    }
  • Zod schema for UpdateRoleConfig. Defines sessionId (required string) and three optional fields: strictMode (boolean), minComplianceScore (number 0-100), requireAlternation (boolean).
    export const UpdateRoleConfigSchema = z.object({
      sessionId: z.string().describe('Session ID'),
      strictMode: z.boolean().optional().describe('Reject non-compliant rounds'),
      minComplianceScore: z.number().optional().describe('Minimum compliance score (0-100)'),
      requireAlternation: z.boolean().optional().describe('Require verifier/critic alternation')
    });
  • Registration entry in the roleTools map with description, schema reference, and handler reference.
    elenchus_update_role_config: {
      description: 'Update role enforcement configuration. Can enable strict mode, change minimum compliance score, or toggle role alternation requirement.',
      schema: UpdateRoleConfigSchema,
      handler: updateRoleConfigTool
    }
  • Core updateRoleConfig function that retrieves the session's role state, merges the partial config update, and returns the new config object.
    export function updateRoleConfig(
      sessionId: string,
      config: Partial<RoleEnforcementConfig>
    ): RoleEnforcementConfig | null {
      const state = roleStates.get(sessionId);
      if (!state) return null;
    
      state.config = { ...state.config, ...config };
      return state.config;
    }
  • Composed tools export that spreads roleTools (including elenchus_update_role_config) into the main tools object.
    // Compose all tools into a single export
    export const tools = {
      ...sessionLifecycleTools,
      ...issueManagementTools,
      ...mediatorTools,
      ...roleTools,
      ...reverifyTools,
      ...diffTools,
      ...cacheTools,
      ...pipelineTools,
      ...safeguardsTools,
      ...optimizationTools,
      ...dynamicRoleTools,
Behavior2/5

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

No annotations provided, so description carries full burden. It indicates a mutation ('update') but fails to disclose any side effects, state changes, or required permissions. Lacks details on what happens if updating partial fields or whether changes are reversible.

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?

Description is a single sentence, concise and direct. However, it could be slightly more structured by separating the purpose from the list of configurable items.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description should explain return values or success signals. It only mentions what can be updated, leaving the agent uninformed about the outcome of the operation.

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?

Input schema has 100% description coverage, so schema already explains each parameter. Description adds value by listing the three optional parameters together, reinforcing their group purpose, but does not provide new semantic details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'update' and the resource 'role enforcement configuration', listing specific configurable aspects. It distinguishes from siblings by saying 'role enforcement configuration', which is unique among the sibling tools listed.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'elenchus_set_dynamic_roles' or 'elenchus_configure_optimization'. Does not specify prerequisites or conditions for use.

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/jhlee0409/elenchus-mcp'

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