ArmorNGlory MCP Server

Official

by ArmorNGlory

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Server Quality Checklist

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

Latest release: v1.0.0
Disambiguation4/5
Most tools target distinct actions (search, details, collections, recommendations, brand info, sizing, checkout, Q&A), but 'search_armornglory_products' and 'answer_faith_fashion_questions' both return products and could be confused. The Q&A tool is more about answering questions, but the overlap in output makes selection slightly ambiguous.
Naming Consistency3/5
Verbs are consistent (search, get, list, generate, answer), but the naming pattern is mixed: some tools include 'armornglory' while others do not (e.g., get_collection_products vs list_armornglory_collections). This inconsistency makes the set feel less predictable, though still readable.
Tool Count5/5
9 tools is well-scoped for an e-commerce brand assistant, covering discovery, details, collections, recommendations, brand info, sizing, checkout, and FAQ. Each tool serves a distinct purpose without redundancy.
Completeness4/5
The surface covers the full customer journey—search, browse, recommend, learn, size, and purchase. Minor gaps exist (e.g., no explicit 'list all products' or order tracking), but these are not essential for the stated purpose and can be worked around.
Average 3.9/5 across 9 of 9 tools scored. Lowest: 3.3/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 5 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
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

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for behavioral disclosure. It says 'Retrieve all products,' but the schema includes a limit parameter (default 10, max 25), so the description is misleading about 'all' and does not mention pagination or limits. It also provides no information about output format, errors, or side effects. The tool is likely read-only, which is implied by 'Retrieve,' but no additional behavioral traits are disclosed.
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 a single sentence that is front-loaded with the action and resource. It includes a long list of examples, which is somewhat redundant given the schema also lists them, but it's not excessive. It is efficient and to the point, though the examples could be trimmed without losing clarity. Overall, it is concise and structured well.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 params, no output schema, no annotations), the description should provide enough context for an agent to understand what happens. It fails to mention that the 'limit' parameter caps the returned products, so it won't actually return 'all' products in most cases. It also does not describe the response format (e.g., product IDs, full details), which is important since there is no output schema. The examples are helpful but do not compensate for these 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 coverage is 100% as both parameters have descriptions. The tool description adds examples of collection handles, but the schema already includes the same examples, so it adds minimal value. The limit parameter is not elaborated beyond the schema's description. Since the schema covers parameters well, the description does not need to add much, but it could clarify that the limit caps the 'all' claim. Baseline of 3 is 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?
The description clearly states 'Retrieve all products belonging to a specific ArmorNGlory collection' with a specific verb (Retrieve) and resource (products). It provides multiple collection handle examples, which distinguishes it from sibling tools like search_armornglory_products that search by keyword, and get_armornglory_product_details that fetch a single product's details.
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 by stating its function (retrieve products for a specific collection), but it does not explicitly mention when to use it versus alternatives, nor provide any exclusions or mention sibling tools. For example, it doesn't say 'use this when you have a collection handle; for keyword search, use search_armornglory_products.' Context is clear but not explicit on alternatives.
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 are provided, so the description must carry the behavioral transparency burden. It does disclose that the tool returns 'SEO-rich explanations and matching ArmorNGlory products with direct buy links,' which is useful output behavior. However, it does not mention whether answers are retrieved from a static knowledge base or generated, or any limitations, rate limits, or access requirements.
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?
The description is two sentences of clean, front-loaded content. The first sentence states the core behavior and topic range; the second states the return value and links. Every sentence earns its place with no filler.
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 low complexity (one parameter, no nested objects, no output schema), the description is reasonably complete: it names the question categories, the return format (explanations and products), and the presence of buy links. The absence of an output schema is compensated by describing the return elements, though it could mention result limits or answer sourcing.
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 input schema covers 100% of the single parameter 'query' with detailed examples, so the schema does the heavy lifting. The description itself adds minimal parameter meaning beyond clarifying the general topic scope, which aligns with the baseline 3 for high schema coverage.
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 begins with a specific verb and resource: 'Search authoritative questions and answers regarding Christian streetwear...' and clearly differentiates itself from sibling tools by focusing on Q&A content, theological meanings, sizing tips, gift ideas, and care guides while also returning matching products and buy links. It is distinct from search_armornglory_products, which is product search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies general usage for answering questions, but it does not provide any explicit when-to-use or when-not-to-use guidance against overlapping siblings like get_sizing_and_fit_guide, recommend_faith_gifts, or search_armornglory_products. This leaves the agent uncertain about which tool to invoke for sizing or gift questions.
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 are provided, so the description must carry the burden. It does disclose the core behavior—a non-mutating recommendation/consulting action—but it does not state what the response looks like, whether it checks live product availability, or how it handles missing optional inputs.
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?
Single sentence, front-loaded with the tool's role ('Smart faith gift consultant'), and packs product categories plus input dimensions without filler. The only minor word is 'Smart,' which doesn't undermine its efficiency.
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?
For a simple recommender, the description plus schema is adequate for basic invocation, but with no output schema and no annotations it leaves gaps: output format, handling of optional parameters, and relationship to product-search siblings are not explained.
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?
All five parameters are documented in the schema (100% coverage), so the description adds no new syntax or format details. It merely restates the parameter dimensions (occasion, budget, style vibe, scripture theme) in prose, which is helpful orientation but not semantic enrichment.
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 uses a specific verb ('recommends') and names the exact resource ('personalized Christian streetwear, hats, EVA foam clogs, and accessories'), with the input dimensions that drive the recommendation. This clearly differentiates it from sibling product-search/detail tools, which are about retrieving existing products rather than acting as a gift consultant.
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 'gift consultant' framing: it should be used when a personalized faith-gift recommendation is needed. However, it never explicitly says when not to use it or names alternatives (e.g., search_armornglory_products for direct product lookup).
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?
With no annotations, the description must carry the burden. It discloses the type of content (charts, measurements, fit guidance) and product line coverage, but it does not describe response format, how results are organized, or any edge-case behavior (e.g., what 'All' returns). It provides basic but not comprehensive behavioral detail.
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?
The description is a single, information-dense sentence that front-loads the action ('Get') and the outcome ('detailed sizing charts, measurements, and fit guidance'). Every word contributes; there is no redundancy or filler.
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 simplicity (one optional param, no output schema), the description adequately covers what the tool returns and for which categories. It could have briefly mentioned what types of measurements (e.g., chest, waist, foot length), but the current level is sufficient for most use cases and consistent with 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?
The schema fully describes the 'category' parameter with an enum and a description. The description adds no additional semantics beyond mentioning the product categories, which are already listed in the enum. Since schema coverage is 100%, the description doesn't need to compensate, but it also doesn't enrich the meaning.
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 verb ('Get') and resource ('detailed sizing charts, measurements, and fit guidance') and specifies the exact product categories covered. This distinguishes it from sibling tools like get_armornglory_product_details or search_armornglory_products, which focus on product info or search rather than sizing.
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 this tool is for sizing-related inquiries but provides no explicit guidance on when to use it versus alternatives. It doesn't mention exclusions or conditions, but the scope (sizing for ArmorGlory products) is inferable from the tool name and description. It lacks explicit 'when to use / when not to use' language.
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 the description carries the burden. It states the core action (generating a link) but does not disclose potential edge cases like invalid variant IDs, whether the operation is idempotent, or any authentication requirements. For a simple URL generator, this is minimally transparent but lacks deeper behavioral detail.
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?
The description is a single, front-loaded sentence that communicates the tool's purpose and scope efficiently. Every word contributes value, with no filler or redundant 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?
The tool is straightforward: input items and optional discount, output a checkout URL. The description sufficiently covers the intent but doesn't mention the return format, error handling, or prerequisites. However, given the simplicity and lack of an output schema, it is reasonably complete for its complexity.
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% (items and discountCode are described). The description adds context about the items but does not introduce new meaning beyond the schema. It mentions '1 or more specific product variant IDs and quantities' which maps to the items array, but no additional parameter semantics are provided, so it meets the baseline for high schema coverage.
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?
Description clearly states the tool generates a direct Shopify checkout URL for specific variant IDs and quantities. It uses a specific verb ('generate') and resource ('direct Shopify checkout URL'), and it distinguishes itself from siblings by focusing on checkout creation, while siblings handle product search, details, collections, etc.
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?
The description implies usage for creating a checkout link with specific items, and mentions the benefit of proceeding directly to payment. It doesn't explicitly state when not to use it or contrast with alternatives, but the purpose is clear enough given the sibling context, so it's adequate without detailed exclusions.
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 are provided, so the description carries the full burden. It discloses that the tool returns descriptions and product counts, and implies a read-only operation via 'List'. It does not mention sorting, pagination behavior, or potential rate limits, but the stated output detail adds value beyond the bare action.
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?
The description is a single, well-structured sentence that starts with the core purpose and includes illustrative examples, providing maximum information with zero fluff.
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?
The tool is low-complexity with one optional parameter and no output schema. The description adequately conveys what is returned (descriptions and product counts) and gives examples, making it sufficiently complete for an agent to understand expected output and usage context.
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 input schema fully documents the only parameter 'limit' with its min/max and default, achieving 100% coverage. The description adds no extra semantic detail about the parameter, so a baseline score of 3 is 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?
The description clearly states the action (list) and resource (curated collections on ArmorNGlory.com), and includes concrete examples like 'Hats & Beanies' and 'Faith Footwear' which distinguish it from sibling tools that focus on products or details.
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 for browsing collections, but does not explicitly contrast with alternative tools like get_collection_products or search_armornglory_products. No when-not or exclusions are provided, so an agent might need to infer from tool names alone.
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 are provided, so the description carries the behavioral burden. It explicitly discloses the search scope ('complete catalog') and the return contents ('product details, prices, images, and direct 1-click checkout links'). While it does not discuss edge behaviors like default limits or matching semantics, the search verb and return description sufficiently convey a read-only lookup behavior.
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?
The description is two concise, front-loaded sentences. The first sentence establishes the tool's purpose and search dimensions; the second sentence specifies the return values. There is no filler, repetition of schema details, or unnecessary elaboration.
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 11 optional parameters, no annotations, and no output schema, the description provides useful completion by naming the return payload and overall search scope. It could be more complete by explicitly stating that results are a list, mentioning the default/pagination behavior, or noting how filters combine, but the schema's well-documented limit parameter fills part of that gap.
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 input schema already documents each parameter with examples. The description adds an overall semantic grouping of filter dimensions, but it does not provide additional meaning beyond the schema's per-parameter descriptions, such as filter combination logic or format nuances.
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 action ('Search') and the specific resource ('the complete ArmorNGlory Christian streetwear catalog'), and it enumerates search dimensions such as keywords, scripture verses, category, aesthetic, color, size, and price range. It also distinguishes itself from siblings like get_armornglory_product_details and list_armornglory_collections by positioning this as the comprehensive catalog search tool that returns product details and checkout links.
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 conveys clear context: use this tool to search across the full ArmorNGlory catalog with many optional filters. However, it does not explicitly say when to prefer this over sibling tools, nor does it mention exclusions or alternatives (e.g., using get_armornglory_product_details for a specific product's full details).
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 are provided, so the description carries the burden. It clearly states the tool is read-only (retrieves information) and lists the specific content areas. However, it doesn't disclose any potential limitations, such as whether the information is static or if there are any access restrictions. The description is adequate but not rich in behavioral detail.
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?
The description is a single, well-structured sentence that front-loads the purpose and lists the specific content areas. It is concise and every word earns its place, with no redundancy or filler.
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 has no parameters, no output schema, and no annotations, the description is complete for its purpose. It clearly states what information will be retrieved. It could be slightly more complete by mentioning the format or structure of the response, but for a simple retrieval tool, it is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description doesn't need to explain parameter semantics. The schema coverage is 100% (no properties), and the description fully explains what the tool returns. This is a baseline 4 for a no-parameter tool.
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 retrieves the official ArmorNGlory brand mission, theology, design ethos, craftsmanship standards, and name meaning. It uses a specific verb ('Retrieve') and resource ('brand mission, theology, design ethos, craftsmanship standards, and meaning behind the name'), distinguishing it from sibling tools that focus on products, collections, or recommendations.
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?
The description implies this tool is for brand-related information, which is distinct from product searches or recommendations. It doesn't explicitly state when not to use it, but the context of sibling tools makes the usage clear. It could be improved by explicitly noting it's for brand context rather than product-specific queries.
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 are provided, so the description carries the full burden. It discloses that the tool returns comprehensive details (theological meaning, fit, care) and checkout links, which is useful. However, it does not mention any side effects, auth requirements, or rate limits, but for a read-only retrieval tool, this is acceptable. Adding explicit mention that it does not modify data would improve transparency.
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?
The description is a single sentence, front-loaded with the core purpose. It efficiently lists the return contents and the accepted identifiers without any filler. Every phrase contributes to understanding the tool's function.
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?
Given one parameter, 100% schema coverage, no output schema, and no annotations, the description is remarkably complete. It tells the agent exactly what information will be returned (theological meaning, craftsmanship, fit, care, checkout links) and what input is needed. There is no ambiguity about the tool's use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers 100% of the parameter (productHandleOrTitle) with a descriptive name and examples. The description adds value by explaining that the parameter can be a handle, title, or ID, and implicitly mentions that it must be specific. With full schema coverage, baseline is 3, but the description re-emphasizes the flexibility of input, earning a 4.
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: to get complete product details for a specific ArmorNGlory item. It specifies the identifying inputs (handle, title, or ID) and lists the types of details returned (theological meaning, craftsmanship, etc.), distinguishing it from sibling tools like search_armornglory_products and list_armornglory_collections.
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?
The description implies when to use this tool: when you need detailed product data, as opposed to searching or listing. It doesn't explicitly say when not to use it or mention alternatives, but the context of siblings and the focus on 'in-depth' details provide clear context. A small gap is not naming alternatives explicitly.
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

Copy to your README.md:

[![armornglory-mcp-server MCP server](https://glama.ai/mcp/servers/ArmorNGlory/armornglory-mcp-server/badges/card.svg)](https://glama.ai/mcp/servers/ArmorNGlory/armornglory-mcp-server)

Score Badge

Copy to your README.md:

[![armornglory-mcp-server MCP server](https://glama.ai/mcp/servers/ArmorNGlory/armornglory-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/ArmorNGlory/armornglory-mcp-server)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/ArmorNGlory/armornglory-mcp-server'

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