makiti-mcp

by seasayDev

Overview Schema Related Servers Score Discussions

JavaScript

Local

Server Quality Checklist

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

Latest release: v1.0.0
Disambiguation4/5
The tools cover distinct shopping functions: broad search, price comparison, deal hunting, price history, and product comparison. product_search and find_best_price both provide pricing but are differentiated by scope and accuracy; descriptions make this clear. Overall, minimal confusion.
Naming Consistency3/5
Names use a mix of noun-verb (product_compare, product_search), verb-noun (find_best_price, find_deals), and noun-noun (price_history, makiti_guide) patterns. While all use snake_case, the inconsistent verb placement makes the naming less predictable.
Tool Count5/5
Six tools is an appropriate size for a shopping assistant, covering core workflows without being overwhelming. Each tool has a defined role.
Completeness5/5
The tool set covers search, price comparison, price history, and deals, which are the main shopping decision processes. A guide tool adds helpful meta-navigation. No significant gaps are apparent.
Average 3.5/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 6 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, the description carries the full burden of behavioral disclosure, but it only says it returns product data. It does not mention whether this is a read-only operation, any rate limits, pagination, or other behaviors. Minimal context beyond the core 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 two sentences, front-loading the action and returning valuable result details without any redundancy. Every word earns its place.
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?
Given the tool has 7 parameters but all are schema-documented, and there is no output schema, the description provides a basic understanding but lacks usage context and behavioral details. It is adequate but has clear gaps for an agent to fully understand when and how to invoke it.
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 provides full descriptions for all 7 parameters, so the baseline is 3. The description adds no additional parameter-specific meaning beyond the schema, though it implies filters like price and retailer are part of the search context.
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 clearly states the tool searches for products across the web and lists the types of returned data (names, prices, retailers, links). It is specific with a verb and resource, but it does not explicitly differentiate from sibling tools like find_best_price or find_deals.
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?
No guidance is provided on when to use this tool versus alternatives such as product_compare or price_history. There are no exclusions, prerequisites, or contextual hints about appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral transparency. It mentions 'track or estimate' but doesn't explain what estimation entails, what data sources are used, or what the return format looks like, leaving significant gaps for an agent that needs to interpret results.
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 action and includes a purpose clause. It is concise, front-loaded, and every word earns its place.
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?
With no annotations and no output schema, the description should explain what the tool returns and how to interpret it. It only states the high-level purpose, leaving the agent uncertain about the result structure (e.g., time series, verdict, or estimate). This is incomplete for effective use.
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 has 100% description coverage for all three parameters (product, days_back, retailers). The tool description adds no extra meaning beyond the schema, so the baseline score of 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 clearly states the tool tracks or estimates price history to determine if a current price is a good deal, giving a specific verb and resource. However, it doesn't explicitly differentiate it from sibling tools like find_best_price or product_compare, which could also be used for deal evaluation.
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 phrase 'to determine if current price is a good deal' implies a clear context for when to use the tool. Yet there is no mention of when not to use it, and no alternatives are named among the sibling tools, leaving the guidance at an implied level.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/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 of behavioral disclosure. The description merely restates the tool's purpose ('Hunt for active deals') and adds synonyms like 'promo codes' and 'discounts,' but it does not disclose whether results are filtered by activeness automatically, whether coupon validity is verified, or what the return structure looks like. This is a significant transparency gap beyond what the name and schema already convey.
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 concise sentence with no redundant or filler content. It is front-loaded with the core action and resource. Every phrase contributes meaning, and it is appropriately sized for a simple search tool.
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?
The tool has 4 parameters, no output schema, and no annotations. The description covers the core query intent but omits return-value details (e.g., does it return a list of deals with prices and coupon codes?), pagination/limit behavior, and regional defaults. Schema descriptions fill gaps on parameters, but the absence of output specification and usage context leaves the overall description only minimally complete for an agent to understand results and boundaries.
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 provides descriptions for all 4 parameters, covering 100% of them. The description itself adds no additional parameter-level detail beyond what the schema already contains. According to the rubric, when schema coverage is high (>80%), the baseline is 3, and there is no evidence of additional semantic value in the description.
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 uses a clear action verb ('Hunt') and specifies the resource: active deals, promo codes, and discounts for a product or category. This distinguishes find_deals from sibling tools like product_search (searching products) and find_best_price (comparing prices). However, 'Hunt' is slightly informal, and the description does not explicitly contrast it with these siblings, so it falls short of a perfect 5.
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 the tool is for finding deals and discounts, and the query parameter is described as 'Product, brand, or category to find deals for.' There is no explicit guidance on when to choose this tool over alternatives like find_best_price or price_history, nor any exclusionary statements. This meets the 'implied usage' level but lacks explicit when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the full burden of behavioral disclosure. It states the tool 'gets guidance' but does not describe the output format, whether it calls other tools, or any side effects. This lack of information leaves the agent uncertain about the tool's actual 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 a single, well-structured sentence that front-loads the primary purpose with no redundant words. It efficiently communicates the tool's function without unnecessary elaboration.
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?
The description gives the essential purpose but lacks details about what the guidance output looks like or how it interacts with sibling tools. Given the absence of an output schema and annotations, the description is minimally sufficient but leaves ambiguity about the tool's actual deliverable.
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 provides 100% coverage for the single 'scenario' parameter, including a description and example. The tool description itself adds no parameter-specific information, but since the schema is self-explanatory, the 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 tool provides guidance on using Makiti tools for shopping decisions, with a specific verb ('Get guidance') and resource ('how to use Makiti tools'). This distinguishes it from sibling tools which directly perform shopping actions like search, compare, or find prices.
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?
No guidance is provided on when to use this tool versus the sibling tools. There is no mention of alternatives, exclusions, or specific scenarios that would trigger its use. The description only implies a purpose without contextual usage direction.
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 is the sole source of behavioral information. It discloses the content of the comparison (specs, prices, pros/cons, verdict) which gives some insight into return format, but it does not mention side effects, data freshness, or any limitations such as whether it performs live lookups.
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 entire description is a single, front-loaded sentence with no redundant words. Every element (compare, two products, output types) contributes to understanding.
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 simple with 100% schema coverage and no output schema, but the description compensates by listing the returned comparison elements (specs, prices, pros/cons, verdict). It could be more complete by noting how optional parameters like budget affect the analysis, but it is adequate for a basic comparison 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?
All four parameters have descriptions in the schema, which covers 100% of parameter semantics. The description does not add extra meaning beyond the schema, as it only mentions 'two products' without detailing how budget or category influence the comparison.
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 opens with a specific verb 'Compare' and resource 'two products', and enumerates the output dimensions (specs, prices, pros/cons, verdict). This clearly differentiates it from sibling tools like product_search and find_best_price.
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 the use case of comparing exactly two products side-by-side, which is clear from the first phrase. However, it does not explicitly state when to prefer this over siblings like find_best_price or price_history, nor does it mention exclusions, so it lacks explicit usage boundaries.
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 transparency burden. It reveals that the tool scrapes live pages and that Best Buy blocks access, but it does not disclose other potential behavioral issues like rate limiting, IP blocks from other retailers, or terms-of-service risks. The description is partially transparent but lacks a fuller safety and reliability disclosure.
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 concise and well-structured: three sentences, each adding meaningful information. It leads with the core action, then differentiates from siblings, and ends with an important caveat. No filler or repetition.
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 simplicity of the tool (3 parameters, no output schema), the description provides good context: it explains the geographic scope, the direct scraping behavior, and a known blocker. However, it does not describe the return value structure or failure handling, which for a scraping tool could be relevant. Still, the core context is sufficiently covered.
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%, so the baseline is 3. The description does not add detailed meaning beyond the schema parameters; it only reinforces that the retailers are Canadian. The schema already explains query, limit, and retailers, so the description adds little incremental value.
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 function: scraping Canadian retailer search pages to find the actual lowest price. It uses specific verbs ('scrape', 'find') and distinguishes itself from sibling product_search by noting it reads live retailer pages, making it more accurate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly contrasts with product_search ('More accurate than product_search because it reads live retailer pages'), providing clear guidance on when to prefer this tool. It also warns that Best Buy Canada blocks automated access, implying not to expect results from that retailer.
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:

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

Score Badge

Copy to your README.md:

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

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/seasayDev/makiti-mcp'

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