Skip to main content
Glama

ask_ask_post

Read-onlyIdempotent

Submit legal questions in Korean or English to route to specialized agents with real-time statute verification for accurate legal guidance.

Instructions

Ask

Main legal question endpoint — routes to 1 of 60 specialist agents with real-time statute verification.

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
queryYesLegal question in Korean or English (max 2000 chars). Example: '부당해고를 당했는데 어떻게 해야 하나요?'
historyNoConversation history (max 6 recent turns). Each item: {role: 'user'|'model', content: '...'}
langNoResponse language: 'ko' (Korean) or 'en' (English). Auto-detected from query if omitted.
current_leaderNoCurrent leader context for handoff/deliberation.
is_first_questionNoWhether this is the user's first question in the session.
Behavior4/5

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

Annotations declare safety properties (readOnly, idempotent), while the description adds valuable operational context: the 60-agent routing architecture and real-time statute verification. It also documents response structures (200/422 codes and validation error schemas), though formatted as REST documentation rather than MCP output schemas.

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 leading 'Ask' header is wasted space, but the subsequent sentence is information-dense. The extensive response documentation (HTTP codes, JSON schemas) is unusual for MCP but justified given the lack of a formal output schema. Content is front-loaded with the behavioral summary before technical details.

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 the lack of a formal output schema in the structured fields, the description compensates by including response schemas and example error formats inline. Combined with 100% input parameter coverage and clear annotations, the description provides sufficient context for invocation, though sibling differentiation would improve it further.

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?

With 100% schema description coverage, the baseline is met. The description text does not add parameter semantics beyond the schema definitions, but this is acceptable given the comprehensive schema documentation (examples, language constraints, nested object 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 opening sentence clearly defines this as the 'Main legal question endpoint' and specifies distinct behavioral characteristics: routing to '1 of 60 specialist agents' with 'real-time statute verification.' This specific verb+resource+mechanism combination distinguishes it from generic 'ask' tools.

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?

While calling it the 'Main' endpoint implies primary usage, there is no explicit guidance on when to use this versus siblings like 'ask_expert_ask_expert_post' or 'ask_stream_ask_stream_post.' No exclusions or alternative recommendations are provided.

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