Skip to main content
Glama

Agent Exchange store

get_recommend

Which brands does one model, llama-3.3-70b on Workers AI, recommend in a category? It answers the buyer questions and every answer is scored. One call returns the ranked leaderboard: each brand's AI-visibility score (0-100), the models that mention it, and the competitors the AI names instead. Use for market research, competitive analysis, lead scoring and brand monitoring. Params: category.

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": "get_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It helpfully discloses the output shape (ranked leaderboard, 0-100 scores, mentioning models, named competitors) and that results come from a single named model. It says nothing about the biggest behavioral fact implied by the schema: that a signed x402 payment payload is required, nor about pricing, limits, or whether calls are billable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening question and the leaderboard sentence are front-loaded and earn their place, and the use-case list is compact. The trailing 'Params: category' is both wasteful and incorrect given the schema, which drags the structure down.

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?

For a single-parameter tool with no output schema, the description does good work enumerating the return payload so an agent knows what it gets back. It is nonetheless incomplete on two things an agent needs to call it successfully: the paid x402 requirement on the only real parameter, and the fact that the 'category' input it advertises is not in the schema.

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?

The schema documents its single parameter (x_payment, signed x402 payment payload) at 100% coverage, which alone would justify a 3. However, the description adds 'Params: category' — a parameter that does not exist in the schema — and never explains x_payment or payment semantics, so it actively misleads about the tool's inputs rather than adding meaning.

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 states a concrete verb and resource ('Which brands does one model ... recommend in a category') and pins the model (llama-3.3-70b on Workers AI), which is genuinely differentiating detail. It does not name the closest siblings (ai_category_ranking, brand_ai_visibility_check, ai_visibility_index), so an agent must infer the distinction from their names alone.

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?

It lists four consumer use cases (market research, competitive analysis, lead scoring, brand monitoring), which gives implied context for when to call it. There is no when-not guidance and no reference to an alternative tool for a different kind of query, so routing relies on the sibling names rather than on this text.

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