Skip to main content
Glama
Sign In
sanhang-mcp

sanhang-mcp

by sanhangkc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

浏览弦图墙

sanhang_gallery
Read-only

Browse public chord-diagram artwork to discover reference styles, see what the service can render, and show similar examples; returns titles, tags, and direct video links.

Instructions

浏览已公开的弦图作品（社区画廊）。可用来了解这套服务能画出什么、找参考风格，或给用户展示同类作品。返回标题、标签与视频直链。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNo关键词，匹配标题与描述。
pageNo页码，默认 1。
tagsNo标签过滤，逗号分隔，如“三角函数,正弦”。
sort_byNo排序：最新 / 最热 / 最多赞。默认最新。created_at
categoryNo二级学科，如 数学/物理学/计算机科学 等，留空表示不过滤。
page_sizeNo每页条数，默认 10，最多 50。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful context beyond them: it restricts scope to public works and discloses the return payload (titles, tags, video direct links), which tells the agent the result is a browsable list with playable media.

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 short sentences: identity first, then use cases, then return shape. Nothing is redundant, and the most decision-relevant information (what it is and what it returns) is front-loaded.

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 six-parameter read-only browsing tool with full schema coverage and no output schema, the description covers purpose, usage and return fields adequately. It omits pagination/total-count behavior, which is minor given that page and page_size are documented in the schema.

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 all six parameters (q, page, tags, sort_by, category, page_size) are already documented in the schema with defaults, ranges and an enum. The description adds no additional semantics about filtering, pagination limits or sort behavior, so baseline 3 applies.

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 and resource in '浏览已公开的弦图作品（社区画廊）' and clarifies the scope as public/community content only. It does not explicitly contrast itself with the sibling tools sanhang_render or sanhang_task, so the distinction must be inferred from the word '浏览' versus rendering or task operations.

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 three concrete use cases: learning what the service can draw, finding reference styles, and showing users similar works. It does not state when-not to use it or name the sibling alternatives, but the positive guidance is strong enough for an agent to route correctly.

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

Deploy Server

Other Tools