Skip to main content
Glama

lawmadi-os

by io.github.peter120525-cmd
OverviewDiscussionsAdmin

get_daily_content

[KEY REQUIRED · no credits, 60/day] 발행된 데일리 콘텐츠 한 편을 전체 레코드 형태로 가져옵니다: 오늘의 법률상식(daily — 검증 조문 목록과 FAQ 포함), 전략 칼럼(strategy)·기술 칼럼(tech, 라이브 확인된 참고자료 포함), 리걸테크 뉴스(news, 출처 도메인 포함), 수험 판례 강의노트(bar), 오늘의 판례(precedent — 검증 판례 레코드 첨부). 날짜를 주거나, 생략하면 해당 스트림의 최신 편. / Fetch one published daily post in full-record form. Pass a date, or omit it for the latest post in that stream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Omit for the latest post.
streamYesContent stream.
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. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers: auth requirement (KEY REQUIRED), cost/quota (no credits, 60/day), and the date-vs-latest defaulting behavior. It stops short of describing failure modes or what 'full record' concretely returns, but the quota and auth disclosures are the high-value facts.

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?

Key constraints are front-loaded in the bracketed prefix before the content explanation. The Korean/English duplication roughly doubles the length, but the English mirrors rather than adds, so no information is wasted, just repeated.

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 three-parameter read tool with no output schema and no annotations, the description covers auth, quota, stream enumeration, and date defaulting — everything needed to call it correctly. Only the concrete shape of the returned 'full record' is left implicit.

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; the description earns more by explaining what each stream value actually yields (daily includes verified provisions and FAQ, tech includes live-verified references, precedent attaches verified case records), which the bare enum does not convey. Date omission semantics are also restated usefully.

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?

States a specific verb and resource ('fetch one published daily post in full-record form') and enumerates the six streams with what each contains, so the agent knows exactly what comes back. It does not, however, differentiate itself from the sibling latest_content, which appears to overlap on the 'omit date for latest' behavior.

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 concrete operating conditions up front (KEY REQUIRED, no credits, 60/day limit) and explains the core usage decision — pass a date or omit it for the latest post in that stream. It never names an alternative tool or states when NOT to use this one, so no explicit exclusion guidance.

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