Firmafakta

Change a saved segment

firmafakta_update

Destructive

Rename a saved segment, replace its expression or change its per (workplace or company), in place, keeping the rest of it. Give its id from firmafakta_load and at least one of name, segment and per. Refused, without charge, for an id the account has not saved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "firmafakta_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	the saved segment's id, from firmafakta_load
`per`	No	what it counts from now on: workplace or company; omitted keeps it
`name`	No	its new name; omitted keeps the name
`segment`	No	its new expression in describe's segment language; omitted keeps the expression

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`usage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / per

Added value: +{
+  "description": "what it counts from now on: workplace or company; omitted keeps it",
+  "enum": [
+    "workplace",
+    "company"
+  ],
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds context beyond the annotations: the update is partial and preserves unspecified fields, and unsaved ids are refused 'without charge' (a billing/error trait). Annotations already declare the safety profile (destructiveHint=true, idempotentHint=false), so this is useful supplementary detail rather than a contradiction.

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?

Two tight sentences: the operation and its variants first, then the calling contract and the refusal case. No filler, and the key constraint is front-loaded.

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?

Return values are covered by the output schema and safety by annotations, and the description covers partial-update semantics, required inputs, and error behavior. Only minor omissions remain, such as whether the update can be undone or what a refusal looks like.

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 coverage is 100%, so baseline is 3, but the description adds a genuine constraint the schema does not express: although only id is required, at least one of name, segment or per must be supplied. It also notes the keep-if-omitted semantics that the schema only states per-field.

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?

States specific verbs (rename, replace, change) against a specific resource (a saved segment) and the scope ('in place, keeping the rest of it'). It is clearly distinguishable from siblings like firmafakta_save, firmafakta_delete and firmafakta_load.

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?

Gives a clear precondition: id from firmafakta_load plus at least one of name, segment, per. It also states an exclusion ('refused... for an id the account has not saved'). It does not explicitly name the alternative tools (save for new, delete for removal), so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Firmafakta tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.