url_htmlFetch a web page and return its rendered HTML source. 입력한 URL의 페이지를 열어 HTML을 추출해 반환합니다. 자바스크립트 렌더링이 필요한 페이지도 처리됩니다. [호출당 5포인트]
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 페이지 URL (예: https://apick.app) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations align with the described fetch behavior. The description adds useful context beyond annotations by disclosing JavaScript rendering support and a per-call cost, both of which help the agent anticipate behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The key purpose is front-loaded in English, and the Korean sentence repeats the same idea but is short. The JavaScript rendering and cost details are valuable. Minor redundancy prevents a higher score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only tool with no output schema, the description covers what it does, what it returns, dynamic rendering behavior, and cost. It is sufficiently complete for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single URL parameter is already fully documented in the schema with a description and example, so the description adds little beyond restating '입력한 URL.' With 100% schema coverage, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb and resource: 'Fetch a web page and return its rendered HTML source.' It distinguishes itself from a screenshot tool by emphasizing HTML source rather than an image, though it does not explicitly name sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies a use case by noting that pages requiring JavaScript rendering are handled, but it does not explicitly state when to prefer this tool over alternatives like url_screenshot or provide any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools target the same documents with unclear boundaries: identi_card_image1, ocr_identi1, and identity_document_id_card all accept a resident registration card image but differ in verification vs extraction vs masking, which agents will struggle to distinguish. The identi_card1-5 vs identi_card_image1-5 vs ocr_identi1-5 clusters are especially confusing, despite some helpful descriptions.
Naming is highly inconsistent: some tools use verb_noun (check_phone_valid, search_juso, pdf_merge), some are bare nouns (whois, nslookup, ocr, stt), and identity tools use three parallel schemes (identi_card1, identi_card_image1, ocr_identi1, identity_document_id_card) with no clear pattern. No single convention is followed across the toolset.
88 tools is an extreme count for a single MCP server, spanning identity verification, parcel tracking, LLM chat, image generation, PDF conversion, TTS, and network lookups. This is an API marketplace dump rather than a focused toolset, and the number far exceeds any reasonable scope.
The server's scope is unbounded, so it has gaps everywhere: no video transcription shortcut, no PDF splitting, no batch cancellation for images (only TTS), and identity clusters lack clear differentiation between verify/extract/mask workflows. Some subdomains like TTS have a full lifecycle, but overall the coverage is scattered and incomplete for the implied breadth.