Skip to main content
Glama
HiroakiKatoh

legal-impact-mapper

by HiroakiKatoh

Update Fact Classification

update_fact_classification

Updates a fact node's text and classification within a FactGraph, locking it after modification to prevent further changes unless unlocked.

Instructions

【いつ使う】弁護士がノードの内容(条文テキストや分類)を変更するとき。extract_fact_graphの出力graphを受け取って呼ぶ。 【入力】graph: 現在のFactGraph / node_id: 変更対象のノードID / new_text: 新しいテキスト / new_type: 新しい分類(任意)/ mark_verified: 変更後にuser_verified=trueでロックするか(デフォルトtrue) 【出力】{ graph: 更新済みFactGraph, changed_node_ids: 変更されたノードIDリスト, diff_summary: { modified_nodes, details } }。changed_node_idsをそのままanalyze_impactに渡すこと。 【注意】user_verified=trueのノードは変更を拒否し、changed_node_ids=[]で返る。再編集が必要な場合はgraph内の該当ノードのuser_verifiedをfalseに書き換えてから再呼び出しすること。mark_verified=true(デフォルト)の場合、変更後のノードは以後自動的にロックされる。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
graphYes現在のFactGraph(extract_fact_graphの出力)
node_idYes変更対象のノードID
new_textYesノードの新しいテキスト
new_typeNoノードの新しい分類タイプ(任意)
mark_verifiedNo変更後にuser_verified=trueとマークするか(デフォルト: true)
Behavior5/5

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

With no annotations, the description fully discloses behavior: user_verified=true blocks modifications, after a successful edit with mark_verified=true the node becomes locked, and the output structure includes changed_node_ids and diff_summary. It also explains the return value when a node is locked.

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?

The description is well-structured with clear sections (use case, input, output, notes) and is appropriately sized. It includes all necessary information without redundancy, though it could be slightly more concise.

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

Completeness5/5

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

The description is highly complete given the tool's complexity (5 parameters, nested objects, no output schema). It covers input, output, edge cases (locked nodes), and integration with sibling tools. No gaps remain.

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. The description adds value by listing parameters in a structured format with their purposes and defaults (e.g., mark_verified defaults to true). It also explains the output structure, which the schema does not provide.

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 explicitly states the verb-resource ('update fact classification') and when to use it (lawyer changes node content). It distinguishes from siblings by mentioning it takes the output of extract_fact_graph and its output is fed to analyze_impact.

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?

The description gives explicit context for usage: 'When a lawyer changes the content of a node (text or classification)'. It also provides exclusion criteria: user_verified=true nodes reject changes, requiring setting user_verified=false first. Additionally, it instructs to pass changed_node_ids to analyze_impact.

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/HiroakiKatoh/legal-impact-mapper'

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