Skip to main content
Glama
konsulto

@konsulto/mcp

Official
by konsulto

konsulto_update_finding

Update scalar fields of a security finding, such as title, severity, status, taxonomy, or assets. Use this tool to modify a finding's metadata without altering its prose body or evidence.

Instructions

Update scalar fields on an existing finding. Use this for changing title, severity, status, taxonomy, or assets — NOT for editing the prose body (use konsulto_append_to_section / konsulto_replace_section for that). NOT for evidence (use konsulto_add_evidence_to_finding).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findingIdYes
patchYes

Implementation Reference

  • src/server.ts:479-519 (registration)
    Registration of the 'konsulto_update_finding' tool via server.tool() with name, description, Zod schema, and handler callback.
    server.tool(
      'konsulto_update_finding',
      'Update scalar fields on an existing finding. Use this for changing ' +
        'title, severity, status, taxonomy, or assets — NOT for editing the ' +
        'prose body (use konsulto_append_to_section / konsulto_replace_section ' +
        'for that). NOT for evidence (use konsulto_add_evidence_to_finding).',
      {
        findingId: z.string(),
        patch: z
          .object({
            title: z.string().optional(),
            severity: z
              .enum(['critical', 'high', 'medium', 'low', 'informative'])
              .optional(),
            status: z
              .enum(['open', 'accepted', 'mitigated', 'closed', 'rejected'])
              .optional(),
            taxonomy: z.any().optional(),
            assets: z.array(z.any()).optional(),
          })
          .passthrough(),
      },
      async ({ findingId, patch }) => {
        try {
          const updated = (await client.put<any>(`/findings/${findingId}`, patch)) as any;
          return ok({
            finding: {
              id: String(updated._id ?? updated.id),
              title: updated.title,
              severity: updated.severity,
              status: updated.status,
            },
            webUrl: client.webUrl(
              `/audits/${updated.auditId}/findings/${updated._id ?? updated.id}`,
            ),
          });
        } catch (err) {
          return errResult(err);
        }
      },
    );
  • Input validation schema: findingId (string) and patch object with optional title, severity enum, status enum, taxonomy, and assets fields.
    {
      findingId: z.string(),
      patch: z
        .object({
          title: z.string().optional(),
          severity: z
            .enum(['critical', 'high', 'medium', 'low', 'informative'])
            .optional(),
          status: z
            .enum(['open', 'accepted', 'mitigated', 'closed', 'rejected'])
            .optional(),
          taxonomy: z.any().optional(),
          assets: z.array(z.any()).optional(),
        })
        .passthrough(),
    },
  • Handler function that calls client.put('/findings/{findingId}', patch) to update the finding, then returns the updated finding ID/title/severity/status and a webUrl.
    async ({ findingId, patch }) => {
      try {
        const updated = (await client.put<any>(`/findings/${findingId}`, patch)) as any;
        return ok({
          finding: {
            id: String(updated._id ?? updated.id),
            title: updated.title,
            severity: updated.severity,
            status: updated.status,
          },
          webUrl: client.webUrl(
            `/audits/${updated.auditId}/findings/${updated._id ?? updated.id}`,
          ),
        });
      } catch (err) {
        return errResult(err);
      }
    },
  • ApiClient.put() helper method used by the handler to make the HTTP PUT request to the backend.
    async put<T = unknown>(
      path: string,
      body?: unknown,
      config?: AxiosRequestConfig,
    ): Promise<T> {
      return this.request<T>({ ...config, method: 'PUT', url: path, data: body });
    }
  • ok() helper that wraps the result payload into an MCP content response.
    function ok(payload: unknown) {
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(payload, null, 2) }],
      };
    }
Behavior3/5

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

No annotations provided, so description carries burden. States it updates scalar fields but lacks details on side effects, permissions, idempotency, or whether it's a partial update. Adequate but could be better.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, each adding distinct value: function, exclusions, and another exclusion. Front-loaded with main purpose. No filler.

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?

Given nested patch object, no output schema, and no annotations, description covers main usage and exclusions well. Could clarify that patch only includes fields to update, but overall complete for decision-making. Good differentiation from 18 sibling tools.

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 coverage is 0%, but description lists updatable fields (title, severity, status, taxonomy, assets), adding meaning. However, does not explain the 'taxonomy' field structure or that patch is a partial update. Partially compensates for schema's lack of 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 clearly states the tool updates scalar fields on an existing finding, listing specific fields (title, severity, status, taxonomy, assets). It distinguishes from siblings by explicitly stating what NOT to use it for, naming alternative tools.

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?

Provides explicit guidance on when to use (changing scalar fields) and when not (prose body, evidence), with named alternatives (konsulto_append_to_section, konsulto_replace_section, konsulto_add_evidence_to_finding).

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/konsulto/konsulto-mcp'

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