Skip to main content
Glama
primadonna-gpters

AgentSkills MCP Server

by primadonna-gpters
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: business_data focuses on Korean business information, code_review analyzes code quality and security, and web_search performs general web searches. There is no overlap in functionality or ambiguity between these tools.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern (business_data, code_review, web_search), which is readable and predictable. The only minor deviation is that 'business_data' uses a compound noun while the others are more action-oriented, but this doesn't break the overall consistency.

    Tool Count3/5

    With only 3 tools, the server feels thin for a general-purpose 'AgentSkills' server. While each tool is distinct, the scope implied by the server name suggests a broader set of agent capabilities might be expected, making this borderline appropriate.

    Completeness3/5

    For a server named 'AgentSkills', there are notable gaps in common agent capabilities such as file operations, data processing, or communication tools. However, the three provided tools cover useful domains (business research, code analysis, web search) without dead ends in their respective areas.

  • Average 3.7/5 across 3 of 3 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations provided, the description bears full responsibility for behavioral disclosure. It identifies the operation as 'look up' (read-only implication) and data types retrieved, but omits critical operational details: error behavior when companies aren't found, data freshness/recency, rate limits, or whether results are structured vs. plain text.

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

    Conciseness4/5

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

    Two sentences efficiently structured: capability declaration followed by use case. No redundancy or filler content, though the second sentence partially overlaps with the schema's explicit mentioning of identification methods.

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

    Completeness3/5

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

    Adequate for a 3-parameter lookup tool with complete schema coverage. However, lacking both annotations and output schema, the description should ideally disclose return value structure or empty-result behavior. As written, it leaves the agent uncertain about response format.

    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 baseline applies. The description mirrors the schema content (mapping enum values to data types and noting the identification alternatives) but does not add syntactic constraints, validation rules, or interaction logic beyond what the schema already documents.

    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?

    Clear verb 'Look up' and specific resource 'Korean business data' with enumerated subtypes (company info, news, financial). However, it lacks explicit differentiation from sibling 'web_search', which could also retrieve company information, leaving the agent to infer the specialization from 'Korean' context.

    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?

    States the tool is 'Useful for researching Korean companies' and identifies the two lookup methods (name or registration number), providing implied context. However, it lacks explicit 'when-not-to-use' guidance or comparison to 'web_search' alternative, leaving ambiguity about when this specialized tool is preferred over general search.

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

  • Behavior3/5

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

    No annotations provided, so description carries full burden. It compensates for missing output schema by describing return values (score, summary, issues, observations). However, lacks operational details like side effects, code privacy/storage policies, or rate limits expected for a code submission tool.

    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 well-structured sentences: first states purpose, second describes output. No redundancy or waste. Front-loaded with the most critical information (what it does) before return value details.

    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?

    Good coverage given constraints: describes output shape to compensate for missing output schema, and all parameters are well-defined in schema. Could improve by noting privacy considerations when submitting code or supported language nuances, but functionally complete for invocation.

    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% with full descriptions for all 3 parameters including enums and defaults. Description doesn't add parameter-specific semantics beyond the schema, but the comprehensive schema makes additional description unnecessary. Baseline 3 appropriate for high-coverage schemas.

    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?

    Clear specific verb ('Analyze') and resource ('code') with scope covering issues, security, and improvements. Clearly distinguishes from siblings 'business_data' and 'web_search' by domain (code analysis vs. business data/web search).

    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?

    Usage is implied by the clear domain description (code analysis), but lacks explicit guidelines on when to use vs. siblings or prerequisites like 'use when you need static analysis' or 'do not use for runtime debugging'.

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

  • Behavior4/5

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

    No annotations provided, so description carries full burden. Discloses 'real-time' nature (fresh data), result structure ('title, URL, snippet'), and AI-generated summary feature. Missing rate limits, auth requirements, or caching behavior, but covers primary behavioral traits well.

    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 efficiently structured sentences with zero waste. First sentence front-loads action and value proposition ('Perform... and get structured results'). Second sentence details output format. Every word earns its place.

    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?

    No output schema exists, but description compensates by detailing return structure (title, URL, snippet, AI summary). 100% input schema coverage reduces documentation burden. Lacks error handling or rate limit disclosure, but complete for a standard search tool.

    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% with clear descriptions for all 3 parameters (query, maxResults, language including defaults). Description adds no parameter-specific semantics beyond the schema, which is acceptable given the complete schema documentation. Baseline 3 appropriate.

    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?

    Clear specific verb ('Perform') + resource ('web search'). Distinguishes effectively from siblings 'business_data' (internal company data) and 'code_review' (code analysis) by specifying 'web' as the domain.

    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?

    Usage is implied by the domain specificity ('web search' vs internal 'business' data), but lacks explicit guidance on when to choose this over 'business_data' for company information or 'code_review' for code-specific queries. No 'when not to use' or prerequisite guidance provided.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

agentskills-mcp MCP server

Copy to your README.md:

Score Badge

agentskills-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/primadonna-gpters/agentskills-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server