Skip to main content
Glama

OpenCurrent

모델·도구·뉴스 정리 받기

get_card
Read-onlyIdempotent

search_catalog로 찾은 카드의 전체 사실 정보(모델: 가격·한도·컨텍스트·API id, 도구: 쓰는 모델·MCP 지원·시작하기, 뉴스 정리: 항목)와 출처, 확인 시점을 받을 때 사용.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes카드 id (kind/slug, 예: model/claude-sonnet-5-5) 또는 웹 주소

Output Schema

NameRequiredDescriptionDefault
idYes카드 id (kind/slug). get_card에 그대로 넘긴다
urlYes사람이 읽는 웹 페이지 주소. 출처로 밝힐 때 쓴다
kindYes
titleYes
fieldsYes종류별 사실 정보. 단위: 토큰, 가격은 100만 토큰당 USD
aliasesYes
curatedYesOpenCurrent 운영자가 책임지는 큐레이션 정보
sourcesYes
summaryYes
kindLabelYes
updatedAtYes
verificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds that results include sources and a verification timestamp, which tells the agent the data is attributed and time-stamped. It says nothing about behavior when the id is unknown or about latency/caching, so it adds only modest value beyond annotations.

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

Conciseness3/5

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

It is a single sentence, but the long parenthetical enumerating the returned fields duplicates what the output schema already specifies. The key precondition (card from search_catalog) is front-loaded, but the field list is clutter rather than value.

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 one-parameter read with full schema coverage, an output schema, and safety annotations, the description supplies the necessary precondition and a sense of returned content. Missing only edge-case behavior (unknown id, URL vs id resolution), which is minor at this 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 coverage is 100% and the single id parameter is fully documented in-schema, including the kind/slug format and URL alternative. The description reinforces that the id comes from search_catalog but adds no format or resolution details beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb+resource: it returns a card's full fact set (model pricing/limits/context/API id, tool model usage/MCP support/getting-started, news digest items) plus sources and verification time. It clearly distinguishes itself from search_catalog, which only locates cards. Slight deduction because the headline phrasing ('받을 때 사용') is a usage clause rather than a crisp statement of what the tool does.

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?

It gives explicit context for use: take a card found via search_catalog and fetch its full details. There are no stated exclusions or when-not conditions, and no alternative beside search_catalog is referenced, but the search-then-get workflow is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources