Toolzy MCP Serverofficial
A
licenseNot graded
qualityB
maintenanceEnables AI assistants to search, view details, and check availability of tool rental listings from Toolzy's peer-to-peer marketplace.
MIT
There's An AI For That
Server Details
Search TAAFT for AI tools and retrieve public tool details.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- taaft/mcp
- GitHub Stars
- 0
Available Tools
2 toolsget_toolAInspect
Get public details for one TAAFT AI tool by slug.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The tool slug returned by search_tools. |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the burden. It discloses that details are 'public' and identifies the lookup mechanism (by slug), but does not describe pagination, response shape, or error behavior for invalid slugs. Acceptable for a simple getter, but with no annotations there is room for more.
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?
One clear sentence that conveys the action, resource, scope, and identifier mechanism with no wasted words.
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?
For a simple single-parameter lookup with no output schema, the description is nearly complete. It could benefit from stating that the slug must come from search_tools, which is already quoted in the description, so essentially complete.
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 single parameter is already documented in the schema. Description adds the source of the slug ('returned by search_tools'), which is useful but does not substantially extend the schema.
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?
States a specific verb ('Get'), resource ('public details for one TAAFT AI tool'), and identifier ('by slug'). Clearly distinguishes from search_tools, which would return multiple tools.
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?
Implied usage: use when you have a specific slug from search_tools. Sibling list includes search_tools, so the agent can infer to use search_tools first, though no explicit when-not-to-use statement is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_toolsAInspect
Search the TAAFT directory for AI tools that match a query.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | default | |
| type | No | ||
| limit | No | ||
| query | Yes | What the user needs an AI tool for. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| tools | Yes |
TDQS
A3.6/5.0
Behavior3/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. The verb 'search' implies a non-destructive read operation, but the description does not disclose any potential limitations, rate limits, or whether it modifies data. While it is likely safe, the lack of explicit disclosure makes this average.
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 clear sentence with no redundant information. It is front-loaded with the core action and resource, making it easy to parse quickly.
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 presence of an output schema and the simplicity of the search tool, the description is adequate but lacks explicit guidance on when to prefer this over get_tool. It also does not mention any usage constraints or additional context that might be helpful, though the schema covers parameter details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25% (only the query parameter has a description). The tool description does not compensate for the other three parameters (sort, type, limit) – it only mentions matching a query. The enums in the schema provide some semantic hints, but the description adds no extra value, so it fails to cover the gap.
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 resource (the TAAFT directory for AI tools). It is specific about matching a query, and the sibling tool get_tool is implied to be for retrieving a specific tool, so the purpose is distinguishable.
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 searching while get_tool is for retrieving a specific tool, but it does not explicitly state when to use this tool versus the alternative. There are no exclusions or conditions provided, so usage guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
search_tools2 fields changed- added
Output schema / properties / tools / items / properties / website_urlAdded value: +{ + "type": [ + "string", + "null" + ] +} - changed
Output schema / properties / tools / items / requiredPrevious value: -[ - "name", - "slug", - "task", - "tagline", - "url" -]New value: +[ + "name", + "slug", + "task", + "tagline", + "url", + "website_url" +]
2 tool updates
- First observed
get_tool - First observed
search_tools
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Query the HokAI catalogue of AI tools, agents, models, companies and infrastructure services.
Search, inspect, recommend, and explain rated AI tools through Agent Radar.
AI-powered SaaS tool discovery API. Search 150+ curated business tools and get recommendations.
Free search across ~35,000 agent tools (x402 bazaar + MCP registry) by plain-language need.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve EU research outputs including publications, datasets, software, and funded projects from OpenAIRE.15MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve information about Terraform providers and modules from the public Terraform registry, including detailed documentation, version information, and resource specifications.12MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search a curated database of 200+ AI tool cards with pricing, platforms, use cases, and source links, so users can ask which tool to use for a task and get grounded recommendations.101MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: one searches the directory by query, the other fetches details for a specific tool by slug. There is no overlap or ambiguity in when to use each.
Naming Consistency5/5
Both tool names follow the same verb_noun snake_case pattern: get_tool and search_tools. The naming is predictable and consistent.
Tool Count3/5
Two tools feels thin for a directory service, but it is a minimal read-only surface. The count is borderline rather than severely lacking.
Completeness4/5
The pair covers the core directory workflow: search to discover tools, then get details for a specific one. Browsing by category or listing all tools could be useful additions, but they are not critical gaps.