Tailor
Tailor Platform for AI assistants: search, list and read the platform documentation.
사용해야 할까요
품질 및 안전성
발견 사항 (1)
- LOWTool 'fetch_knowledge' suggests web access but openWorldHint=falsefetch_knowledge에서
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"mcp": {
"url": "https://mcp.tailor.tech/"
}
}
}원격 엔드포인트
https://mcp.tailor.tech/streamable-http할 수 있는 일
도구 목록
도구 (3)
🟢fetch_knowledge(id, section)
Return the Markdown source of one documentation page, addressed by an id from search_knowledge or list_knowledge. The first line is the page's URL, for citation. Long pages come back as a heading outline instead; pass section to read one part of them.
입력 스키마
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "page identifier exactly as returned by search_knowledge or list_knowledge, for example docs:sdk/quickstart.md"
},
"section": {
"type": "string",
"description": "return only this section of the page, matched case-insensitively against its level-two headings"
}
},
"required": [
"id"
],
"additionalProperties": false
}🟢list_knowledge(source, section)
List the documentation table of contents: the id, title, source, section and summary of every page. Use this to see what exists when a search does not find the right words; prefer search_knowledge when you know what you are looking for. Narrow the listing with source or section, since the full listing is large and is cut at 500 entries.
입력 스키마
{
"type": "object",
"properties": {
"source": {
"type": "string",
"description": "restrict the listing to one knowledge source; omit to list every source"
},
"section": {
"type": "string",
"description": "restrict the listing to one table-of-contents section, matched case-insensitively"
}
},
"additionalProperties": false
}🟢search_knowledge(query, source, limit)
Search the body text of Tailor Platform's public documentation and return matching pages with an excerpt. Start here for most questions, then pass an id to fetch_knowledge to read a page in full. Matching is literal and case-insensitive, so prefer the exact terms that would appear in the docs. This covers published documentation only; it cannot see a user's own application data.
입력 스키마
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "words to look for in the documentation body, matched case-insensitively as a substring"
},
"source": {
"type": "string",
"description": "restrict the search to one knowledge source; omit to search every source"
},
"limit": {
"type": "integer",
"description": "maximum number of pages to return; defaults to 10, capped at 50"
}
},
"required": [
"query"
],
"additionalProperties": false
}커뮤니티
증거