Skip to main content
Glama
antegral

MMA MCP Server

by antegral
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Server Quality Checklist

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

  • Latest release: v1.0.0

  • Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_designated_entities' has a single, clear purpose focused on searching for designated entities related to military service exemptions.

    Naming Consistency5/5

    The tool name 'search_designated_entities' follows a consistent verb_noun pattern (search + designated_entities). Since there is only one tool, there are no inconsistencies or deviations to evaluate, making it perfectly consistent.

    Tool Count2/5

    A single tool is too few for a server that appears to cover military service exemption entities, as it lacks basic operations like creating, updating, or deleting entities, and may not support comprehensive workflows. This feels thin and incomplete for the apparent scope.

    Completeness2/5

    The tool set is severely incomplete for the domain of military service exemption entities. While the search tool exists, there are obvious gaps such as no CRUD operations (e.g., create, update, delete entities), no detailed entity retrieval, or other lifecycle management tools, which will likely cause agent failures in broader tasks.

  • Average 3.9/5 across 1 of 1 tools scored.

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

    • 1 of 1 community issues answered or closed 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 is failing

  • This repository is licensed under MIT License.

  • 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

  • Behavior4/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it specifies the output format (CSV), result limit (maximum 30 companies), and that it's a read-only search operation (implied by '검색합니다' and '조회할 수 있습니다'). However, it doesn't mention potential rate limits, authentication requirements, or error conditions.

    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?

    The description is appropriately concise with three sentences that each serve a clear purpose: stating the tool's function, specifying the types of companies searched, and describing output format and limits. It's front-loaded with the core functionality, though the second sentence could be slightly more streamlined.

    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?

    Given the tool's moderate complexity (8 parameters, no output schema, no annotations), the description provides good contextual completeness. It covers the tool's purpose, scope, output format, and result limits. The main gap is the lack of output schema, but the description compensates by specifying CSV format and maximum result count, though it doesn't detail the CSV structure.

    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?

    The schema description coverage is 100%, so the schema already documents all 8 parameters thoroughly with descriptions and enums. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 where the schema does the heavy lifting without additional value from the description.

    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 description clearly states the tool's purpose with specific verbs ('검색합니다', '조회할 수 있습니다') and resources ('병역일터', '병역특례 지정업체'), specifying the exact data source and target entities. It distinguishes the tool by mentioning the three specific military service types it supports, making its scope explicit even without siblings.

    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?

    The description implies usage context by stating what types of companies can be searched (those supporting specific military service types), but it doesn't provide explicit guidance on when to use this tool versus alternatives. Since no sibling tools are listed, there's no opportunity for comparison, but it lacks information about prerequisites or typical use cases beyond the basic functionality.

    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

agent-for-agent MCP server

Copy to your README.md:

Score Badge

agent-for-agent 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/antegral/agent-for-agent'

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