Skip to main content
Glama

Citemark

Get AI picks for a software category

get_ai_picks
Read-onlyIdempotent

Returns the products ChatGPT, Gemini and Claude recommend most in a software category, ranked by how often they are named across a fixed set of buyer questions that Citemark asks every two weeks, with each product's share of answers and average position.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "get_ai_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesThe software category: screenshot-apis (Screenshot APIs), transactional-email (Transactional email services), product-analytics (Product analytics tools), privacy-friendly-analytics (Privacy-friendly web analytics), uptime-monitoring (Uptime monitoring tools), error-tracking (Error tracking tools), feature-flags (Feature flag tools), form-builders (Online form builders), newsletter-platforms (Newsletter platforms), ai-coding-assistants (AI coding assistants).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation, but the description adds real behavioral context beyond them: the data is derived from a fixed set of buyer questions Citemark asks every two weeks, and results are ranked by naming frequency. It does not say how many products are returned or how staleness between biweekly runs is handled, which keeps it from a 5.

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?

A single sentence that front-loads what is returned and then adds ranking methodology. It is dense with chained clauses, but every clause contributes information and nothing is redundant.

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?

There is no output schema, so the description must carry return-value context, and it does: each product's share of answers and average position. For a one-parameter read-only lookup this is nearly complete, with only result-count and freshness-between-refreshes details missing.

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% with a fully enumerated category parameter, so the schema carries the specification burden. The description only restates that the category scopes the recommendation set, adding no extra meaning such as how category choice affects question coverage or result depth.

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?

Specific verb and resource: returns the products that ChatGPT, Gemini and Claude recommend most in a named software category, ranked by frequency across a defined question set. It is clearly distinct from sibling tools like get_my_tracking or check_ai_visibility, which are about the caller's own tracking/visibility rather than model recommendations.

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 description: ask for a category to get aggregated model picks. There is no explicit when-to-use vs. when-not guidance, no mention of how it relates to check_ai_visibility or get_my_tracking, and no stated prerequisites.

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