Skip to main content
Glama

OpenCurrent

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

search_catalog
Read-onlyIdempotent

모델의 능력·가격·컨텍스트 길이·출시일, AI 도구·에이전트의 기능과 쓰는 법, 기간별 AI 뉴스 정리를 찾을 때 사용. OpenCurrent 운영자가 공식 문서로 확인한 큐레이션 정보. 이름(예: 'Claude Sonnet 5.5', 'Cursor')이나 상황으로 찾고, 전체 내용은 get_card로 받을 것.

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": {
      "query": "<query>"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomodel(모델), tool(도구·에이전트), digest(뉴스 정리)로 좁히기
limitNo최대 개수, 기본 5
queryYes모델·도구 이름이나 찾는 내용
capabilityNo이 기능을 가진 도구만 (D100). 활용법의 capabilities id

Output Schema

NameRequiredDescriptionDefault
noteYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly=true, idempotent=true, and openWorld=false, so the safety profile is covered. Beyond that, the description adds meaningful facts: the data is operator-curated from official documentation, results are summarized entries whose full text lives in another tool, and matching works by entity name or by situational description. That 'results are summaries, not full documents' point is exactly the kind of detail annotations cannot convey.

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?

Three sentences, front-loaded with the use case, then provenance, then the handoff to get_card. Nothing is repeated and there is no filler; each sentence carries a distinct piece of information the agent needs.

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?

An output schema exists, so return-value description is not required, and the description covers the content domain, the two query strategies, and the follow-up call. The remaining gap is freshness/cadence of the curated content and any boundary against the sibling search tools, which leaves the agent slightly under-informed when several search tools could apply.

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 description coverage is 100%, so the meaning of query, kind, capability, and limit is already documented at the field level, including enum values and the default limit of 5. The description restates the query parameter's two modes (name vs. situation) and gives name examples such as 'Claude Sonnet 5.5' and 'Cursor', but adds nothing about kind, capability, or limit beyond what the schema says. Baseline 3 applies when the schema carries the load.

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 definition names a specific resource set (model capabilities/pricing/context length/release date, AI tool/agent features and usage, period-based AI news digests) and a specific action (search by name or by situation). It also states the provenance (curated by OpenCurrent operators, verified against official docs), which tells the agent this is a curated index rather than live web data, and it distinguishes itself from get_card, which returns full content.

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 clear trigger conditions ('when looking for' models, AI tools, or news digests) and an explicit next step: use get_card to retrieve the full content, which is a real routing rule. However, it never states when not to use it or how it relates to the sibling search_workflows, so an agent facing a generic query has no stated boundary.

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