Skip to main content
Glama

QuiroAds Clinic Marketing Tools

About QuiroAds

about_quiroads
Read-onlyIdempotent

Facts about QuiroAds, the publisher of these tools: what the agency does, its four free agent skills and how to install them, its free report on the cost of a new chiropractic patient, and links to its services and contact pages. Use it only when the user asks about QuiroAds. lang: en (default) or es.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_quiroads"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en (default) or es.
languageNoSame as lang.

Output Schema

NameRequiredDescriptionDefault
langYes
brandYesWhat QuiroAds is, in one line
pricesYesQuiroAds publishes no prices
reportYesThe free report on the cost of a new chiropractic patient, in English and in Spanish
skillsYesThe free agent skills (the playbooks of get_clinic_marketing_playbook)
contactYes
websiteYes
mcp_docsYesThe docs page of this MCP server
servicesYesThe service pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds context the annotations cannot: this is a static self-description endpoint whose payload is limited to publisher facts and links, which tells the agent there is no live business data here. It does not mention freshness or whether the content is cached.

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?

It is a single front-loaded sentence with the resource first and the restraint clause second, and the itemized content list genuinely helps an agent judge relevance. The enumeration of skills and links is slightly dense, but nothing is 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?

An output schema exists, so the description need not explain return shape, and it correctly spends its words on what topics the answers cover. Combined with a defaultable single-purpose parameter, an agent has everything needed to call it correctly. The only minor gap is no mention of whether the returned links are localized for the requested language.

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% and both parameters are fully documented enums, so the schema carries the parameter burden. The trailing "lang: en (default) or es" merely restates the schema and adds no meaning about what changes between languages. Baseline 3 applies.

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 names the resource precisely (facts about QuiroAds, the publisher) and enumerates the concrete content an agent will get: agency description, four free agent skills plus install steps, a report on chiropractic patient acquisition cost, and links to services/contact. This is clearly distinguishable from the sibling calculation and playbook tools, which produce numbers or marketing guidance rather than publisher metadata.

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?

It gives an explicit negative gate -- "Use it only when the user asks about QuiroAds" -- which is exactly the disambiguation an agent needs to avoid calling this for chiropractic marketing questions that belong to the sibling tools. It stops short of naming those alternatives, so the routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources