Skip to main content
Glama
Sign In
alipay-mcp-server

alipay-mcp-server

by Chromatic0618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_skill_detail

Retrieve the complete SKILL.md content for any AI skill, including pricing, integration instructions, and API documentation, by specifying its name or path.

Instructions

Get full details of a specific AI skill by its name or path. Returns the complete SKILL.md content including pricing, integration instructions, and API documentation.

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": {
      "skill": "<skill>"
    },
    "name": "get_skill_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesSkill name (e.g. 'mbti', 'alipay-aipay') or full API path (e.g. '/api/skill/mbti')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Clearly states return content (complete SKILL.md with pricing, integration, API docs). Does not mention error cases or permissions, but for a read-only tool it's sufficient.

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?

Two sentences, no wasted words. Purpose and return value clearly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with one well-documented parameter and no output schema, the description fully explains what the tool does and returns. No gaps.

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 already covers parameter with examples (skill name or path). Description reiterates 'by its name or path' without adding new meaning. Schema coverage is 100%, so baseline 3.

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?

Specific verb 'Get' plus resource 'full details of a specific AI skill' clearly states purpose. Distinguishes from siblings: discover_skills (listing), get_alipay_* (specific integration).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use when needing skill details, but no explicit guidance on when to use vs siblings like discover_skills or when not to use. Lacks alternatives or exclusions.

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