Skip to main content
Glama

Get Lupamundo's picks

recommend
Read-onlyIdempotent

Products Lupamundo recommends for a need (language courses and apps, exam prep, travel eSIM, kit items...), each with who it is not for, price, and a partner link. Falls back to the most relevant guides when there is no pick yet. Responses include a disclosure field stating that some links are affiliate links.

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": {
      "need": "<need>"
    },
    "name": "recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesThe user's goal, e.g. 'prepare IELTS General to emigrate to Canada'
countryNoUser's country, ISO 3166-1 alpha-2 (MX, ES, CO, CL, AR, PE, US...)

Output Schema

NameRequiredDescriptionDefault
noteNo
picksYes
guidesNo
disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered by structured data. The description adds real context on top: the fallback to guides when no pick exists, the presence of a disclosure field flagging affiliate links, and the 'who it is not for' framing. It stops short of explaining paging or how many picks come back.

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?

Two sentences, no filler, and the core capability is front-loaded before the fallback and disclosure caveats. Every clause carries distinct information an agent would act on.

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?

With an output schema present, the description needn't enumerate return values, yet it helpfully flags the disclosure field and the guide-fallback path. The one gap for an agent choosing between tools is the absence of explicit sibling differentiation, which the richer structured fields do not supply.

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 both `need` and `country` documented in-schema including a concrete IELTS example and a pattern. The description reinforces the `need` concept ('for a need') but adds no syntax, formatting, or fallback semantics for `country`, so the baseline 3 applies.

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 names a concrete resource (recommended products for a stated need) and enumerates the returned fields (who it is not for, price, partner link), so an agent knows exactly what it gets. It doesn't explicitly contrast itself with the sibling guide tools, though the fallback sentence implies the relationship.

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 only implied: give a need and get picks. There is no statement of when to prefer this over search_guides or get_guide, nor any prerequisite or exclusion. The fallback-to-guides sentence describes internal behavior rather than telling the agent when to call this tool versus a sibling.

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