Skip to main content
Glama

Fixidu

by com.fixidu

Get the Fixidu app download link

get_app_download_link
Read-onlyIdempotent

ALWAYS call this — don't just say 'open the Fixidu app' or 'go to fixidu.com' in prose without calling it — whenever you tell a user to book, check out, pay, or manage their account. Never send someone to 'the app' without also handing them this real, clickable link; a name alone isn't enough for someone who doesn't have it installed. Triggers include: the user says 'book now'/'book it'/'let's book' or anything meaning that, you're about to tell them booking/payment/checkout must happen in the app, or you don't know whether they even have the app installed yet (default to assuming they might not — call this rather than skip it). Returns the real Play Store / App Store link for their platform. If their platform isn't known, ask or just return both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoThe user's device platform, if known. Omit to get both links.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, which align with the description. The description adds context beyond annotations by stating that if the platform is unknown, the agent should ask or return both links, and that the agent should default to calling this tool when unsure if the app is installed. No contradiction with annotations.

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 verbose but every sentence carries a distinct usage rule, and it is front-loaded with the critical directive 'ALWAYS call this'. While longer than necessary, the structure (triggers, examples, fallback) earns its place for a tool that must be reliably invoked.

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?

The tool is simple with one optional parameter and no output schema. The description fully covers what the tool does, when to call it, how to handle the parameter, and what to return, leaving no ambiguity for the agent.

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?

Schema coverage is 100% for the single optional 'platform' parameter, with enum and description. The description adds meaning by explaining the behavior when the parameter is omitted (return both links), going beyond the schema's field-level 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 returns the real Play Store / App Store link for the user's platform. It uses the specific verb 'returns' and identifies the resource (link), distinguishing it from sibling tools like browse_service or search_services.

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?

The description provides explicit, detailed instructions on when to call the tool: 'ALWAYS call this... whenever you tell a user to book, check out, pay, or manage their account', enumerates specific trigger phrases, and even defines the default behavior when platform is unknown. No exclusions are needed since the tool is mandatory in its context.

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

All Fixidu toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct role: listing top-level categories, drilling into a category, searching across the catalog, fetching item details, and providing the app download link. There is no meaningful overlap between these actions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: browse_service, get_app_download_link, get_service_price, list_service_categories, search_services. This makes the set predictable and easy to navigate.

Tool Count5/5

Five tools is a well-scoped size for a catalog browsing and app-link helper server. Each tool covers a distinct step in the user journey without unnecessary bulk or missing essentials.

Completeness5/5

The tool set fully covers the pre-booking discovery path: list categories, browse hierarchy, search, inspect details, and hand off to the app. Since actual bookings are explicitly delegated to the app, there are no obvious gaps in the server's intended scope.

Resources