Skip to main content
Glama
peter120525-cmd

LAWMADI

by peter120525-cmd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

chat_leader_api_chat_leader_post

Read-onlyIdempotent

Start a live chat with a legal specialist leader to ask questions about Korean law and receive streaming responses.

Instructions

Chat Leader

1:1 chat with a specific legal specialist leader via SSE streaming.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

Output Schema:

{}

422: Validation Error Content-Type: application/json

Example Response:

{
  "detail": [
    {
      "loc": [],
      "msg": "Message",
      "type": "Error Type"
    }
  ]
}

Output Schema:

{
  "properties": {
    "detail": {
      "items": {
        "properties": {
          "loc": {
            "items": {},
            "type": "array",
            "title": "Location"
          },
          "msg": {
            "type": "string",
            "title": "Message"
          },
          "type": {
            "type": "string",
            "title": "Error Type"
          }
        },
        "type": "object",
        "required": [
          "loc",
          "msg",
          "type"
        ],
        "title": "ValidationError"
      },
      "type": "array",
      "title": "Detail"
    }
  },
  "type": "object",
  "title": "HTTPValidationError"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leader_idYesLeader identifier (e.g. 'L01', 'L32', 'CCO'). Use GET /api/leaders to see all available leaders.
queryYesQuestion to ask the specific leader (max 2000 chars).
historyNoConversation history with this leader.

Tool Definition Quality

C2.9/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it uses SSE streaming, which is behavioral context. However, it lacks details on how state is managed or what side effects occur, so it provides only marginal extra value over annotations.

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

Conciseness2/5

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

The description is verbose, including unnecessary details about response codes and output schemas after the initial purpose statement. The core message is front-loaded, but the excess information reduces conciseness.

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?

The tool is a streaming chat with a leader, but the description does not explain how the SSE streaming works, how history is used, or what the response format is. The output schema is empty, leaving agents unaware of the response structure. This is incomplete for the tool's complexity.

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 description coverage is 100%, with each parameter already well-documented in the schema. The description adds no further parameter semantics, so it meets the baseline of 3.

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 states '1:1 chat with a specific legal specialist leader via SSE streaming', specifying the action (chat) and the resource (legal specialist leader). However, the title in annotations is 'Chat with Legal Agent', which is clearer. The description could differentiate more from sibling 'ask' tools but is sufficient.

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 explicit guidance on when to use this tool versus siblings like ask_post or ask_expert_post. The description does not mention prerequisites or alternatives, leaving the agent without context for selection.

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/peter120525-cmd/lawmadi-os-v60'

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