Skip to main content
Glama

MyFSS

by kr.eocpa

최신 문서 목록

list_recent
Read-onlyIdempotent

MyFSS MCP의 list_recent 도구는 최신 문서 목록을 게시일 내림차순으로 반환합니다.

[Purpose]

  • Query-less skim of "what came out lately", optionally narrowed by 게시판.

[Usage]

  1. "최근 자료 뭐 있어" → (인자 없음 — limit=20)

  2. "감리 지적사례 최신 10건" → board="sanction_case", limit=10

  3. "금융위 보도자료 최신" → board="fsc_press"

[Response]

  • { results:[{ntt_id, date, board, source, title, nature, topics, depts, summary, url}] }

  • No total/offset — this tool has no pagination, and no snippet (there is no query).

[Rules]

  • board takes the English key while the response returns the 한글 라벨 — same asymmetry as search_documents; never feed the response board back as a parameter.

  • Sorted by 게시일(date) — retroactively registered old documents never surface as new.

  • For period/topic narrowing or larger volumes use search_documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardNo게시판 필터
limitNo최대 결과 수 (기본 20)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful behavioral context beyond them: no pagination, no total/offset, no snippet, ordering by publish date, and the subtle point that retroactively registered old documents never surface as new. No contradiction with annotations.

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

Conciseness5/5

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

The description is exceptionally well structured with [Purpose], [Usage], [Response], and [Rules] sections. Every section earns its place and important caveats are front-loaded before deeper behaviors.

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?

Given the tool has no output schema, the description supplies the response shape, the absence of pagination and snippet, sort behavior, and routing to search_documents for larger/narrower queries. This is complete enough for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds crucial semantics not present in the schema: board uses English keys while responses return Korean labels, and includes a warning not to feed the response board back as a parameter. The usage examples also clarify valid value mappings and the limit default.

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?

States a specific verb and resource: returns the recent document list sorted by publish date descending. The [Purpose] section explicitly frames it as a query-less skim, and contrasts it with search_documents, making differentiation clear.

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?

Provides concrete natural-language usage examples that map directly to parameter values, and explicitly says to use search_documents for period/topic narrowing or larger volumes. This gives the agent both when-to-use and when-not-to-use guidance.

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

All MyFSS toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation4/5

Each tool has a distinct role: search_documents handles query-based search with pagination, list_recent is the no-query recent feed, list_tags supplies filter vocabulary, get_document retrieves full text, and get_usage_stats is server telemetry. The only mild overlap is between list_recent and a query-less search_documents, but the descriptions explicitly separate quick skim from fuller search.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_document, get_usage_stats, list_recent, list_tags, search_documents. The naming is predictable and makes the purpose of each tool immediately clear.

Tool Count5/5

Five tools is well-scoped for a read-only regulatory document search and retrieval server. The set covers discovery, search, vocabulary validation, full-text access, and usage monitoring without redundant or excessive tools.

Completeness5/5

The core workflow is fully covered: discover documents via search or recent listing, validate filter values via list_tags, and retrieve full text with pagination via get_document. Since this is a read-only corpus, the absence of create/update/delete tools is appropriate rather than a gap.

Resources