Skip to main content
Glama

lawmadi-os

by io.github.peter120525-cmd
OverviewDiscussionsAdmin

chat_leader

[KEY REQUIRED · charged — see get_pricing] 특정 리더와 1:1로 대화합니다. get_leaders에서 얻은 leader_id(예: 'L01', 'L32', 'CCO')를 넘기세요. 하루 무료 5회를 넘기면 추가 이용에 크레딧이 듭니다 — 그때는 비용을 알려 주는 응답이 오고, confirm: true 로 다시 부를 때만 차감합니다(기본값 false, 확인 없이는 절대 차감하지 않습니다). / Chat 1:1 with a specific legal leader. Provide the leader_id (e.g. 'L01', 'L32', 'CCO') from get_leaders. Past the free daily allowance the call returns the exact cost; credits are spent only when you retry with confirm: true (default false). Pass history when continuing a conversation — otherwise the leader asks the same follow-up questions again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesQuestion to ask the leader (max 2000 chars).
confirmNoSpend credits when the free daily allowance is used up. Default false — nothing is ever charged without this. Only set it after a call returned status 'payment_required' telling you the cost.
historyNo이전 대화. 이것을 안 보내면 서버는 매 호출을 **첫 대화**로 보고 같은 것을 또 되묻습니다 — 리더가 물어본 뒤 답을 줄 때는 그 두 턴을 반드시 함께 넘기세요. 최근 20턴까지 반영됩니다. / Prior turns. Without this the server treats every call as a fresh conversation and asks the same questions again — when you answer a leader's follow-up, send those turns here. Up to 20 recent turns are used.
leader_idYesLeader identifier (e.g. 'L01'). See get_leaders.
client_tagNo선택. client_tag: 호출자 식별용, **응답에 영향 없음**(8~64자, 영숫자·_-.). 서버 로그에만 남아 호출을 골라 세는 데 씁니다. 형식이 어긋나면 무시합니다 — 거절하지 않습니다. 질의 본문에 섞지 마세요: 본문에 넣으면 질문의 일부가 되어 분류와 검증 결과가 달라집니다. / Optional caller label (8-64 chars). Logged only; never affects the response. Invalid values are ignored, not rejected. Do not put it in the query text — there it becomes part of the question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / client_tag
      Added value: +{
+  "description": "선택. client_tag: 호출자 식별용, **응답에 영향 없음**(8~64자, 영숫자·_-.). 서버 로그에만 남아 호출을 골라 세는 데 씁니다. 형식이 어긋나면 무시합니다 — 거절하지 않습니다. 질의 본문에 섞지 마세요: 본문에 넣으면 질문의 일부가 되어 분류와 검증 결과가 달라집니다. / Optional caller label (8-64 chars). Logged only; never affects the response. Invalid values are ignored, not rejected. Do not put it in the query text — there it becomes part of the question.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / history
      Added value: +{
+  "description": "이전 대화. 이것을 안 보내면 서버는 매 호출을 **첫 대화**로 보고 같은 것을 또 되묻습니다 — 리더가 물어본 뒤 답을 줄 때는 그 두 턴을 반드시 함께 넘기세요. 최근 20턴까지 반영됩니다. / Prior turns. Without this the server treats every call as a fresh conversation and asks the same questions again — when you answer a leader's follow-up, send those turns here. Up to 20 recent turns are used.",
+  "items": {
+    "properties": {
+      "content": {
+        "type": "string"
+      },
+      "role": {
+        "enum": [
+          "user",
+          "assistant"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "role",
+      "content"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Spend credits when the free daily allowance is used up. Default false — nothing is ever charged without this. Only set it after a call returned status 'payment_required' telling you the cost.",
+  "type": "boolean"
+}
  4. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the key requirement, charging model, free daily allowance, cost notification, and the confirm-gate that prevents charges. It also explains the server's fresh-conversation behavior without history.

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 front-loaded with the critical '[KEY REQUIRED · charged]' warning and then packs in essential usage details. The Korean/English duplication makes it longer than necessary, but each section still earns its place.

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?

For a paid, history-sensitive tool with no output schema and no annotations, the description covers the key operational rules: ID source, charging protocol, confirmation flow, and history behavior. It does not describe the normal response shape, but what it does cover is sufficient for correct invocation.

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 the baseline is 3, but the description adds real value beyond the schema: it explains why history matters, when confirm should be true, and how client_tag is ignored. These enrich the agent's ability to call parameters correctly.

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?

The description clearly identifies the action ('Chat 1:1 with a specific legal leader') and the resource (leader_id from get_leaders, with examples). It is specific enough to distinguish from generic 'ask' siblings, though it does not explicitly name an alternative tool or draw the boundary.

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?

The description gives concrete usage context: obtain leader_id from get_leaders, pass history when continuing, and set confirm only after a payment_required response. It lacks explicit 'when not to use' guidance versus siblings like ask_expert, but the intended scenarios are clear.

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

All lawmadi-os toolsInspect
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.

Resources